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.

Published: 2023-06-09 Last update: 2025-01-06 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2023-2455 is rated Low Risk (36.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.21%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-2455

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.28% 0.21% -0.07%
2 2025-11-18 0.22% 0.28% +0.06%
3 2025-04-15 0.22%

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-2455

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.4 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 2.5 [email protected]
5.4 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 2.5 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2023-2455

OS Trackers for CVE-2023-2455

vendor priority summary link
alpine CVE-2023-2455: 5 source package rows (postgresql, postgresql12, postgresql13, postgresql14, postgresql15); 32 state rows across 12 repos (3.17-community, 3.17-main, 3.18-community, 3.18-main, 3.19-community, 3.19-main, 3.20-community, 3.20-main, 3.21-community, 3.22-community, edge-community, edge-main); fixed 21, open 11. https://security.alpinelinux.org/vuln/CVE-2023-2455
debian not yet assigned CVE-2023-2455 not yet assigned priority: Debian including 2 source packages (postgresql-13, postgresql-15), 2 status rows across 2 suites (bookworm, bullseye): resolved 2. https://security-tracker.debian.org/tracker/CVE-2023-2455
redhat medium https://access.redhat.com/security/cve/CVE-2023-2455
suse high CVE-2023-2455 severity important: SUSE including 568 source package names (14.8-11.1:libpq5-15.3-150200.5.9.1, 14.8-11.1:postgresql14-14.8-150200.5.26.1, …), 1831 product×package rows across 76 product lines (Container suse/postgres, Image SLES15-SP3-Manager-4-2-Server-BYOS-Azure, … (76 product lines)): Fixed 1072, Known Not Affected 528, Known Affected 231. https://www.suse.com/security/cve/CVE-2023-2455/
ubuntu medium CVE-2023-2455 medium priority: Ubuntu including 8 source packages (postgresql, postgresql-10, …), 104 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 82, ignored 11, released 5, needs-triage 4, deferred 1, not-affected 1. https://ubuntu.com/security/CVE-2023-2455

Affected software / configurations for CVE-2023-2455

Vendor Product Version Raw CPE
postgresql postgresql >= 11.0, < 11.20 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 12.0, < 12.15 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 13.0, < 13.11 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 14.0, < 14.8 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 15.0, < 15.3 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
redhat software_collections cpe:2.3:a:redhat:software_collections:-:*:*:*:*:*:*:*
redhat enterprise_linux 8.0 cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*
redhat enterprise_linux 9.0 cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:*
fedoraproject fedora 38 cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*

References for CVE-2023-2455

cvelogic Threat Intelligence