medium
5.4
CWE
1250
Advisory Published
Updated

CVE-2024-10976: PostgreSQL row security below e.g. subqueries disregards user ID changes

First published: Thu Nov 14 2024(Updated: )

Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended. <a href="https://access.redhat.com/security/cve/CVE-2023-2455">CVE-2023-2455</a> and <a href="https://access.redhat.com/security/cve/CVE-2016-2193">CVE-2016-2193</a> 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.

Credit: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

Affected SoftwareAffected VersionHow to fix
PostgreSQL>=12.0<12.21
PostgreSQL>=13.0<13.17
PostgreSQL>=14.0<14.14
PostgreSQL>=15.0<15.9
PostgreSQL>=16.0<16.5
PostgreSQL>=17.0<17.1
debian/postgresql-13<=13.16-0+deb11u1
13.20-0+deb11u1
debian/postgresql-15
15.12-0+deb12u2
15.10-0+deb12u1
debian/postgresql-17
17.4-1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2024-10976?

    CVE-2024-10976 has a high severity rating due to the risk of unauthorized data access.

  • How do I fix CVE-2024-10976?

    To fix CVE-2024-10976, update PostgreSQL to a secure version as specified in the vendor's security advisory.

  • Which PostgreSQL versions are affected by CVE-2024-10976?

    CVE-2024-10976 affects PostgreSQL versions 13.16-0+deb11u1 and earlier, 15.8-0+deb12u1 and earlier, and 16.4-3 and earlier.

  • What type of vulnerability is CVE-2024-10976?

    CVE-2024-10976 is an incomplete tracking vulnerability in PostgreSQL related to row security.

  • Is CVE-2024-10976 easily exploitable?

    Yes, the vulnerability can be easily exploited if an attacker has access to reused queries.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203