{ "data_type": "CVE", "data_format": "MITRE", "data_version": "4.0", "CVE_data_meta": { "ID": "CVE-2023-2455", "ASSIGNER": "secalert@redhat.com", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "vendor_name": "n/a", "product": { "product_data": [ { "product_name": "postgresql", "version": { "version_data": [ { "version_value": "PostgreSQL 15.3, PostgreSQL 14.8, PostgreSQL 13.11, PostgreSQL 12.15, PostgreSQL 11.20" } ] } } ] } } ] } }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "CWE-20" } ] } ] }, "references": { "reference_data": [ { "refsource": "MISC", "name": "https://access.redhat.com/security/cve/CVE-2023-2455", "url": "https://access.redhat.com/security/cve/CVE-2023-2455" }, { "refsource": "MISC", "name": "https://www.postgresql.org/support/security/CVE-2023-2455/", "url": "https://www.postgresql.org/support/security/CVE-2023-2455/" }, { "refsource": "CONFIRM", "name": "https://security.netapp.com/advisory/ntap-20230706-0006/", "url": "https://security.netapp.com/advisory/ntap-20230706-0006/" } ] }, "description": { "description_data": [ { "lang": "eng", "value": "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." } ] } }