Vulnerability Details CVE-2024-10976
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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.001
EPSS Ranking 26.1%
CVSS Severity
CVSS v3 Score 4.2
Products affected by CVE-2024-10976
-
cpe:2.3:a:postgresql:postgresql:12.0
-
cpe:2.3:a:postgresql:postgresql:12.1
-
cpe:2.3:a:postgresql:postgresql:12.10
-
cpe:2.3:a:postgresql:postgresql:12.11
-
cpe:2.3:a:postgresql:postgresql:12.12
-
cpe:2.3:a:postgresql:postgresql:12.13
-
cpe:2.3:a:postgresql:postgresql:12.14
-
cpe:2.3:a:postgresql:postgresql:12.15
-
cpe:2.3:a:postgresql:postgresql:12.16
-
cpe:2.3:a:postgresql:postgresql:12.17
-
cpe:2.3:a:postgresql:postgresql:12.18
-
cpe:2.3:a:postgresql:postgresql:12.19
-
cpe:2.3:a:postgresql:postgresql:12.2
-
cpe:2.3:a:postgresql:postgresql:12.20
-
cpe:2.3:a:postgresql:postgresql:12.3
-
cpe:2.3:a:postgresql:postgresql:12.4
-
cpe:2.3:a:postgresql:postgresql:12.5
-
cpe:2.3:a:postgresql:postgresql:12.6
-
cpe:2.3:a:postgresql:postgresql:12.7
-
cpe:2.3:a:postgresql:postgresql:12.8
-
cpe:2.3:a:postgresql:postgresql:12.9
-
cpe:2.3:a:postgresql:postgresql:13.0
-
cpe:2.3:a:postgresql:postgresql:13.1
-
cpe:2.3:a:postgresql:postgresql:13.10
-
cpe:2.3:a:postgresql:postgresql:13.11
-
cpe:2.3:a:postgresql:postgresql:13.12
-
cpe:2.3:a:postgresql:postgresql:13.13
-
cpe:2.3:a:postgresql:postgresql:13.14
-
cpe:2.3:a:postgresql:postgresql:13.15
-
cpe:2.3:a:postgresql:postgresql:13.16
-
cpe:2.3:a:postgresql:postgresql:13.2
-
cpe:2.3:a:postgresql:postgresql:13.3
-
cpe:2.3:a:postgresql:postgresql:13.4
-
cpe:2.3:a:postgresql:postgresql:13.5
-
cpe:2.3:a:postgresql:postgresql:13.6
-
cpe:2.3:a:postgresql:postgresql:13.7
-
cpe:2.3:a:postgresql:postgresql:13.8
-
cpe:2.3:a:postgresql:postgresql:13.9
-
cpe:2.3:a:postgresql:postgresql:14.0
-
cpe:2.3:a:postgresql:postgresql:14.1
-
cpe:2.3:a:postgresql:postgresql:14.10
-
cpe:2.3:a:postgresql:postgresql:14.11
-
cpe:2.3:a:postgresql:postgresql:14.12
-
cpe:2.3:a:postgresql:postgresql:14.13
-
cpe:2.3:a:postgresql:postgresql:14.2
-
cpe:2.3:a:postgresql:postgresql:14.3
-
cpe:2.3:a:postgresql:postgresql:14.4
-
cpe:2.3:a:postgresql:postgresql:14.5
-
cpe:2.3:a:postgresql:postgresql:14.6
-
cpe:2.3:a:postgresql:postgresql:14.7
-
cpe:2.3:a:postgresql:postgresql:14.8
-
cpe:2.3:a:postgresql:postgresql:14.9
-
cpe:2.3:a:postgresql:postgresql:15.0
-
cpe:2.3:a:postgresql:postgresql:15.1
-
cpe:2.3:a:postgresql:postgresql:15.2
-
cpe:2.3:a:postgresql:postgresql:15.3
-
cpe:2.3:a:postgresql:postgresql:15.4
-
cpe:2.3:a:postgresql:postgresql:15.5
-
cpe:2.3:a:postgresql:postgresql:15.6
-
cpe:2.3:a:postgresql:postgresql:15.7
-
cpe:2.3:a:postgresql:postgresql:15.8
-
cpe:2.3:a:postgresql:postgresql:16.0
-
cpe:2.3:a:postgresql:postgresql:16.1
-
cpe:2.3:a:postgresql:postgresql:16.2
-
cpe:2.3:a:postgresql:postgresql:16.3
-
cpe:2.3:a:postgresql:postgresql:16.4
-
cpe:2.3:a:postgresql:postgresql:17.0