Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2023-2455: Row security policies disregard user ID changes after inlining; PostgreSQL could permit incorrect policies to be applied in certain cases wh

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.70% (FIRST EPSS); higher than 53.1% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: CBL Mariner 2.0 ARM 14.8-1; CBL Mariner 2.0 x64 14.8-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to CBL Mariner 2.0 ARM 14.8-1; CBL Mariner 2.0 x64 14.8-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.4 · v3.1—No exploit Fix available
Published
Jun 9, 2023
Updated
Jun 17, 2026
EPSS
0.7% · 53th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-2455

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
postgresqlpostgresql
redhatsoftware collections
redhatenterprise linux
fedoraprojectfedora

Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)

Watch new CVEs for postgresql

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is PostgreSQL on your server exposed to the internet?

The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.

Run a port scan

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • postgresql postgresql11.0 and later · before 11.20
  • postgresql postgresql12.0 and later · before 12.15
  • postgresql postgresql13.0 and later · before 13.11
  • postgresql postgresql14.0 and later · before 14.8
  • postgresql postgresql15.0 and later · before 15.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a postgresql

    • PostgreSQL 15.3, PostgreSQL 14.8, PostgreSQL 13.11, PostgreSQL 12.15, PostgreSQL 11.20affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8pg_repackbefore 1.4.6-3.module_el8.6.0+3094+eb237fb81.4.6-3.module_el8.6.0+3094+eb237fb8
AlmaLinux:8pg_repackbefore 1.4.8-1.module_el8.8.0+3487+43ec1b9f1.4.8-1.module_el8.8.0+3487+43ec1b9f
AlmaLinux:8pg_repackbefore 1.4.6-3.module_el8.6.0+2760+1746ec941.4.6-3.module_el8.6.0+2760+1746ec94
AlmaLinux:8pg_repackbefore 1.4.6-3.module_el8.6.0+3095+ee60d9101.4.6-3.module_el8.6.0+3095+ee60d910
AlmaLinux:8pg_repackbefore 1.4.6-3.module_el8.6.0+2758+4f4474df1.4.6-3.module_el8.6.0+2758+4f4474df
AlmaLinux:8pgauditbefore 1.4.0-5.module_el8.6.0+2758+4f4474df1.4.0-5.module_el8.6.0+2758+4f4474df
AlmaLinux:8pgauditbefore 1.4.0-5.module_el8.6.0+3094+eb237fb81.4.0-5.module_el8.6.0+3094+eb237fb8
AlmaLinux:8pgauditbefore 1.5.0-1.module_el8.6.0+2760+1746ec941.5.0-1.module_el8.6.0+2760+1746ec94
AlmaLinux:8pgauditbefore 1.5.0-1.module_el8.6.0+3095+ee60d9101.5.0-1.module_el8.6.0+3095+ee60d910
AlmaLinux:8pgauditbefore 1.7.0-1.module_el8.8.0+3487+43ec1b9f1.7.0-1.module_el8.8.0+3487+43ec1b9f
AlmaLinux:8postgres-decoderbufsbefore 0.10.0-2.module_el8.6.0+3095+ee60d9100.10.0-2.module_el8.6.0+3095+ee60d910
AlmaLinux:8postgres-decoderbufsbefore 0.10.0-2.module_el8.6.0+2760+1746ec940.10.0-2.module_el8.6.0+2760+1746ec94
AlmaLinux:8postgres-decoderbufsbefore 1.9.7-1.Final.module_el8.8.0+3487+43ec1b9f1.9.7-1.Final.module_el8.8.0+3487+43ec1b9f
AlmaLinux:8postgres-decoderbufsbefore 0.10.0-2.module_el8.6.0+3094+eb237fb80.10.0-2.module_el8.6.0+3094+eb237fb8
AlmaLinux:8postgres-decoderbufsbefore 0.10.0-2.module_el8.6.0+2758+4f4474df0.10.0-2.module_el8.6.0+2758+4f4474df
AlmaLinux:8postgresqlbefore 15.3-1.module_el8.8.0+3610+f1fe582015.3-1.module_el8.8.0+3610+f1fe5820
AlmaLinux:8postgresqlbefore 10.23-2.module_el8.8.0+3599+77865fc610.23-2.module_el8.8.0+3599+77865fc6
AlmaLinux:8postgresqlbefore 13.11-1.module_el8.8.0+3601+ca64e76913.11-1.module_el8.8.0+3601+ca64e769
AlmaLinux:8postgresqlbefore 12.15-1.module_el8.8.0+3600+3833017212.15-1.module_el8.8.0+3600+38330172
AlmaLinux:8postgresql-contribbefore 13.11-1.module_el8.8.0+3601+ca64e76913.11-1.module_el8.8.0+3601+ca64e769
AlmaLinux:8postgresql-contribbefore 15.3-1.module_el8.8.0+3610+f1fe582015.3-1.module_el8.8.0+3610+f1fe5820
AlmaLinux:8postgresql-contribbefore 12.15-1.module_el8.8.0+3600+3833017212.15-1.module_el8.8.0+3600+38330172
AlmaLinux:8postgresql-contribbefore 10.23-2.module_el8.8.0+3599+77865fc610.23-2.module_el8.8.0+3599+77865fc6
AlmaLinux:8postgresql-docsbefore 10.23-2.module_el8.8.0+3599+77865fc610.23-2.module_el8.8.0+3599+77865fc6

+96

Other highest-scoring records for the same primary product.

  • CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote attackers
    57Plan
  • CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to
    55Plan
  • CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.
    49Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-41862Mar 3, 2023 · In PostgreSQL, a modified, unauthenticated server can send an unterminated string during the establishment of Kerberos transport encryption.
    14Monitor
  • ← EarlierCVE-2023-2454Jun 9, 2023 · schema_element defeats protective search_path changes; It was found that certain database calls in PostgreSQL could permit an authed attacke
    28Monitor
  • Later →CVE-2023-39418Aug 11, 2023 · Postgresql: merge fails to enforce update or select row security policies
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
CBL Mariner 2.0 ARM14.8-1 · postgresqlMicrosoft (MSRC)
CBL Mariner 2.0 x6414.8-1 · postgresqlMicrosoft (MSRC)
almalinux:postgresql13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-contrib13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-docs13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-plperl13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-plpython313.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-pltcl13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-private-devel13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-private-libs13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-server13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-server-devel13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-static13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-test13.11-1.el9_2 · AlmaLinux:9Package registry (OSV)
alpine:postgresql13.11-r0 · Alpine:v3.13Package registry (OSV)
alpine:postgresql1313.11-r0 · Alpine:v3.15Package registry (OSV)
alpine:postgresql1414.8-r0 · Alpine:v3.15Package registry (OSV)
alpine:postgresql1515.3-r0 · Alpine:v3.17Package registry (OSV)
debian:postgresql-1111.20-0+deb10u1 · Debian:10Package registry (OSV)
debian:postgresql-1313.11-0+deb11u1 · Debian:11Package registry (OSV)
debian:postgresql-1515.3-0+deb12u1 · Debian:12Package registry (OSV)
opensuse:postgresql1111.20-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:postgresql1212.15-150200.8.44.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:postgresql1313.11-150200.5.40.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:postgresql1414.8-150200.5.26.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:postgresql1515.3-150200.5.9.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:postgresql1616.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:postgresql1717.6-2.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:postgresql0:13.11-1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:postgresql-contrib0:13.11-1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+22

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records