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.
History

Mon, 06 Jan 2025 18:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2025-01-06T17:13:23.297Z

Reserved: 2023-05-01T00:00:00

Link: CVE-2023-2455

cve-icon Vulnrichment

Updated: 2024-08-02T06:26:08.921Z

cve-icon NVD

Status : Modified

Published: 2023-06-09T19:15:09.313

Modified: 2025-01-06T18:15:13.913

Link: CVE-2023-2455

cve-icon Redhat

Severity : Moderate

Publid Date: 2023-05-11T00:00:00Z

Links: CVE-2023-2455 - Bugzilla