Total vulnerabilities in the database
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.
| Software | From | Fixed in |
|---|---|---|
| postgresql / postgresql | 15.0 | 15.3 |
| postgresql / postgresql | 14.0 | 14.8 |
| postgresql / postgresql | 13.0 | 13.11 |
| postgresql / postgresql | 12.0 | 12.15 |
| postgresql / postgresql | 11.0 | 11.20 |
| redhat / enterprise_linux | 8.0 | 8.0.x |
| redhat / enterprise_linux | 9.0 | 9.0.x |
| fedoraproject / fedora | 38 | 38.x |