Описание
CloudNativePG is a platform designed to manage PostgreSQL databases within Kubernetes environments. Prior to 1.29.1 and 1.28.3, the CloudNativePG metrics exporter opens its PostgreSQL connection as the postgres superuser via the pod-local Unix socket, then demotes the session with SET ROLE pg_monitor. SET ROLE changes only current_user; session_user remains postgres. Any SQL expression evaluated inside the scrape session can invoke RESET ROLE to recover real superuser privileges, then use COPY ... TO PROGRAM to spawn an OS-level subprocess as the postgres user inside the primary pod. The READ ONLY transaction flag does not block this; it gates writes to database state, not external processes. This vulnerability is fixed in 1.29.1 and 1.28.3.
A flaw was found in CloudNativePG's metrics exporter. The issue arises because the metrics exporter connected to PostgreSQL using a highly privileged account and did not properly restrict privileges during monitoring operations. A low-privileged database user could exploit this behavior through crafted monitoring queries or PostgreSQL object resolution manipulation to regain PostgreSQL superuser privileges and potentially execute arbitrary operating system commands as the postgres user inside the affected database pod.
Отчет
This vulnerability affects CloudNativePG's monitoring and metrics export functionality. The attacker may exploit the affected monitoring functionality to escalate privileges within the PostgreSQL environment and potentially execute arbitrary operating system commands as the postgres user inside the affected database pod. Red Hat Product Security has rated this issue as an Important severity vulnerability rather than Critical. A successful exploitation requires access to a valid database account. A low-privileged authenticated database user (PR:L) is needed. Although exploitation may result in PostgreSQL superuser access and command execution within the affected pod, the impact remains limited to the affected PostgreSQL and container environment. It does not lead to container escape, Kubernetes cluster compromise, or host level privilege escalation. Therefore, Scope is assessed as Unchanged (S:U). Because successful exploitation may allow disclosure, modification, or disruption of database contents, as well as arbitrary command execution within the affected pod, Red Hat assessed the Confidentiality, Integrity, and Availability impacts as High (C:H/I:H/A:H).
Меры по смягчению последствий
- Avoid using unqualified identifiers in custom monitoring queries
- Restrict ownership of user-controlled schemas and database objects
- Avoid unnecessary exposure of monitoring query configuration to untrusted users
- Avoid using broad monitoring configurations such as:
target_databases: '*'unless all databases and users are trusted.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Openshift Data Foundation 4 | odf4/devicefinder-rhel9 | Not affected | ||
| Red Hat Openshift Data Foundation 4 | odf4/mcg-rhel9-operator | Not affected | ||
| Red Hat Openshift Data Foundation 4 | odf4/ocs-metrics-exporter-rhel9 | Affected | ||
| Red Hat Openshift Data Foundation 4 | odf4/ocs-rhel9-operator | Affected | ||
| Red Hat Openshift Data Foundation 4 | odf4/odf-cli-rhel9 | Not affected | ||
| Red Hat Openshift Data Foundation 4 | odf4/odf-cloudnative-pg-rhel9-operator | Affected | ||
| Red Hat Openshift Data Foundation 4 | odf4/odf-multicluster-rhel9-operator | Affected | ||
| Red Hat Openshift Data Foundation 4 | odf4/odf-rhel9-operator | Not affected |
Показывать по
Дополнительная информация
Статус:
EPSS
8.8 High
CVSS3
Связанные уязвимости
CloudNativePG is a platform designed to manage PostgreSQL databases within Kubernetes environments. Prior to 1.29.1 and 1.28.3, the CloudNativePG metrics exporter opens its PostgreSQL connection as the postgres superuser via the pod-local Unix socket, then demotes the session with SET ROLE pg_monitor. SET ROLE changes only current_user; session_user remains postgres. Any SQL expression evaluated inside the scrape session can invoke RESET ROLE to recover real superuser privileges, then use COPY ... TO PROGRAM to spawn an OS-level subprocess as the postgres user inside the primary pod. The READ ONLY transaction flag does not block this; it gates writes to database state, not external processes. This vulnerability is fixed in 1.29.1 and 1.28.3.
CloudNativePG's metrics exporter allows privilege escalation to PostgreSQL superuser and OS RCE
EPSS
8.8 High
CVSS3