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.
References
Link | Resource |
---|---|
https://access.redhat.com/security/cve/CVE-2023-2455 | Third Party Advisory |
https://security.netapp.com/advisory/ntap-20230706-0006/ | |
https://www.postgresql.org/support/security/CVE-2023-2455/ | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
History
No history.
Information
Published : 2023-06-09 19:15
Updated : 2023-07-06 19:15
NVD link : CVE-2023-2455
Mitre link : CVE-2023-2455
CVE.ORG link : CVE-2023-2455
JSON object : View
Products Affected
fedoraproject
- fedora
postgresql
- postgresql
redhat
- enterprise_linux
- software_collections
CWE