PostgreSQL row security below e.g. subqueries disregards user ID changes
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| n/a | PostgreSQL | unaffected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | |||
| postgresql:12-8100020241122084405.489197e6 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2024:10785 | 2024-12-04T00:00:00Z |
| postgresql:15-8100020241122084744.489197e6 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2024:10830 | 2024-12-05T00:00:00Z |
| postgresql:16-8100020241122085009.489197e6 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2024:10831 | 2024-12-05T00:00:00Z |
| postgresql:13-8100020241122084628.489197e6 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2024:10832 | 2024-12-05T00:00:00Z |
| Red Hat Enterprise Linux 9 | |||
| postgresql:15-9050020241122141928.rhel9 | cpe:/a:redhat:enterprise_linux:9 | RHSA-2024:10787 | 2024-12-04T00:00:00Z |
| postgresql:16-9050020241122142517.rhel9 | cpe:/a:redhat:enterprise_linux:9 | RHSA-2024:10788 | 2024-12-04T00:00:00Z |
| postgresql-0:13.18-1.el9_5 | cpe:/a:redhat:enterprise_linux:9 | RHSA-2024:10791 | 2024-12-04T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3954-1 | postgresql-13 security update |
Debian DSA |
DSA-5812-1 | postgresql-15 security update |
EUVD |
EUVD-2024-33374 | Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended. CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes. They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy. This has the same consequences as the two earlier CVEs. That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy. An attacker must tailor an attack to a particular application's pattern of query plan reuse, user ID changes, and role-specific row security policies. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. |
Ubuntu USN |
USN-7132-1 | PostgreSQL vulnerabilities |
Ubuntu USN |
USN-7358-1 | PostgreSQL vulnerabilities |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.769% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Postgresql
Postgresql postgresql |
|
| Weaknesses | NVD-CWE-noinfo | |
| CPEs | cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Postgresql
Postgresql postgresql |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat
Redhat enterprise Linux |
|
| CPEs | cpe:/a:redhat:enterprise_linux:8 cpe:/a:redhat:enterprise_linux:9 |
|
| Vendors & Products |
Redhat
Redhat enterprise Linux |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended. CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes. They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy. This has the same consequences as the two earlier CVEs. That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy. An attacker must tailor an attack to a particular application's pattern of query plan reuse, user ID changes, and role-specific row security policies. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. | |
| Title | PostgreSQL row security below e.g. subqueries disregards user ID changes | |
| Weaknesses | CWE-1250 | |
| References |
| |
| Metrics |
cvssV3_1
|