CVE-2024-10976
PostgreSQL row security below e.g. subqueries disregards user ID changes
Reported by postgresql · Published November 14, 2024
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| postgresql-14 | Chainguard | 14.24-r2, 14.14-r0 |
| postgresql16-test-rpm-macros | Amazon Linux | 16.5-1.amzn2023.0.1 |
| postgresql15-upgrade-devel | Amazon Linux | 15.9-1.amzn2023.0.1 |
| postgresql16 | Amazon Linux | 16.5-1.amzn2023.0.1 |
| postgresql-13 | Wolfi | 13.17-r0 |
| postgresql15-server-devel | Amazon Linux | 15.9-1.amzn2023.0.1 |
| postgresql15-private-devel | Amazon Linux | 15.9-1.amzn2023.0.1 |
| postgresql | Bitnami | 17.1.0, 16.5.0, 15.9.0, 14.14.0, 13.17.0 |
| postgresql-16 | Wolfi | 16.5-r0 |
| postgresql15-test | Amazon Linux | 15.9-1.amzn2023.0.1 |
| postgresql15-plpython3 | Amazon Linux | 15.9-1.amzn2023.0.1 |
| postgresql16-llvmjit | Amazon Linux | 16.5-1.amzn2023.0.1 |
41 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | PostgreSQL | 17, 16, 15 |
| n/a | PostgreSQL | 17, 16, 15 |
Timeline
- Nov 14, 2024 Coalition ESS Score (23 in total, the first dated here)
- Nov 14, 2024 CVE Published
- Nov 14, 2024 PoC Published (7 in total, the first dated here)
- Nov 15, 2024 EPSS Score (30 in total, the first dated here)
- Jun 2, 2026 Security Advisory (33 in total, the first dated here)
- Oct 23, 2026 Distribution Patch (23 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-10976
vulnetix vdb fixes CVE-2024-10976
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-10976/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart