Row security policies disregard user ID changes after inlining; PostgreSQL could permit incorrect policies to be applied in certain 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.
2023-06-09T19:15:09.313
2025-01-06T18:15:13.913
Modified
CVSSv3.1: 5.4 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | postgresql | postgresql | < 11.20 | Yes |
| Application | postgresql | postgresql | < 12.15 | Yes |
| Application | postgresql | postgresql | < 13.11 | Yes |
| Application | postgresql | postgresql | < 14.8 | Yes |
| Application | postgresql | postgresql | < 15.3 | Yes |
| Application | redhat | software_collections | - | Yes |
| Operating System | redhat | enterprise_linux | 8.0 | Yes |
| Operating System | redhat | enterprise_linux | 9.0 | Yes |
| Operating System | fedoraproject | fedora | 38 | Yes |