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 applications 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.
The product has or supports multiple distributed components or sub-systems that are each required to keep their own local copy of shared data - such as state or cache - but the product does not ensure that all local copies remain consistent with each other.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | RedHat | postgresql:12-8100020241122084405.489197e6 | * |
| Red Hat Enterprise Linux 8 | RedHat | postgresql:15-8100020241122084744.489197e6 | * |
| Red Hat Enterprise Linux 8 | RedHat | postgresql:16-8100020241122085009.489197e6 | * |
| Red Hat Enterprise Linux 8 | RedHat | postgresql:13-8100020241122084628.489197e6 | * |
| Red Hat Enterprise Linux 9 | RedHat | postgresql:15-9050020241122141928.rhel9 | * |
| Red Hat Enterprise Linux 9 | RedHat | postgresql:16-9050020241122142517.rhel9 | * |
| Red Hat Enterprise Linux 9 | RedHat | postgresql-0:13.18-1.el9_5 | * |
| Postgresql-12 | Ubuntu | focal | * |
| Postgresql-12 | Ubuntu | upstream | * |
| Postgresql-14 | Ubuntu | jammy | * |
| Postgresql-14 | Ubuntu | upstream | * |
| Postgresql-16 | Ubuntu | devel | * |
| Postgresql-16 | Ubuntu | noble | * |
| Postgresql-16 | Ubuntu | oracular | * |
| Postgresql-16 | Ubuntu | upstream | * |
| Postgresql-9.3 | Ubuntu | trusty/esm | * |
In highly distributed environments, or on systems with distinct physical components that operate independently, there is often a need for each component to store and update its own local copy of key data such as state or cache, so that all components have the same “view” of the overall system and operate in a coordinated fashion. For example, users of a social media service or a massively multiplayer online game might be using their own personal computers while also interacting with different physical hosts in a globally distributed service, but all participants must be able to have the same “view” of the world. Alternately, a processor’s Memory Management Unit (MMU) might have “shadow” MMUs to distribute its workload, and all shadow MMUs are expected to have the same accessible ranges of memory. In such environments, it becomes critical for the product to ensure that this “shared state” is consistently modified across all distributed systems. If state is not consistently maintained across all systems, then critical transactions might take place out of order, or some users might not get the same data as other users. When this inconsistency affects correctness of operations, it can introduce vulnerabilities in mechanisms that depend on consistent state.