CyberRota Analysis
AI-GeneratedPostgreSQL versions prior to 18.5, 17.11, 16.15, 15.19, and 14.24 are vulnerable due to inadequate tracking of changes in role membership and attributes, allowing cached row-level security policies to persist despite modifications. This can lead to unauthorized access, as users may exploit stale policies to perform actions that should be restricted. Organizations using affected PostgreSQL versions should prioritize remediation to mitigate potential privilege escalation risks.
Original NVD Description
Incomplete tracking in PostgreSQL of changes to role membership, role attributes, and database ownership allows a query to continue using cached row-level security policies after those changes require a different policy, via plan reuse. Stale policies continue until some other event invalidates the cache or connection termination ends the session. This permits a user to complete reads and modifications that were recently permitted but now forbidden. An attacker must tailor an attack to a particular application's pattern of privilege removal and role-specific row security policies. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.