Improper input validation in PostgreSQL
CVE-2023-2455
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.
Vulnerability class: Drupalgeddon 2 (CVE-2018-7600)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.4 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N.
EPSS exploit prediction
EPSS 0.007, 53.7th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- PostgreSQL
- Fedoraproject Fedora — versions 38
- Red Hat Enterprise Linux — versions 8.0, 9.0
- Red Hat Software Collections
- PostgreSQL — versions PostgreSQL 15.3, PostgreSQL 14.8, PostgreSQL 13.11, PostgreSQL 12.15, PostgreSQL 11.20
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (lekctut/sdb-hw-13-01, pedr0alencar/vlab-metasploitable2). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- access.redhat.com/security/cve/CVE-2023-2455 (Third Party Advisory)
- www.postgresql.org/support/security/CVE-2023-2455/ (Vendor Advisory)
- security.netapp.com/advisory/ntap-20230706-0006/