Skip to content
Noroxi
NVD / CVE Program· CNA PostgreSQL

CVE-2024-10977: PostgreSQL libpq retains an error message from man-in-the-middle

Noroxi assessment

Priority: Monitor (action score 14/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.39% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: n/a PostgreSQL 12.21, 13.17, 14.14; azl3 postgresql 16.4-2 on Azure Linux 3.0 16.5-1; azl3 postgresql 16.5-1 on Azure Linux 3.0 16.5-1.

Low priority for now. Upgrade to n/a PostgreSQL 12.21, 13.17, 14.14; azl3 postgresql 16.4-2 on Azure Linux 3.0 16.5-1; azl3 postgresql 16.5-1 on Azure Linux 3.0 16.5-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

Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application. For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results. This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.

LowCVSS 3.7 · v3.1—No exploit Fix available
Published
Nov 14, 2024
Updated
Jun 17, 2026
EPSS
0.3% · 34th percentile

Report tools

JSON

Action score

14

Monitor

Low priority for now.

CVSS
14 / 40 · 3.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
3.7
CNA · PostgreSQL
3.1
0.6 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-2024-10977

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for postgresql records

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

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.

Don't want an account? Get "Exploited this week" by email every Monday

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 postgresql12.0 and later · before 12.21
  • postgresql postgresql13.0 and later · before 13.17
  • postgresql postgresql14.0 and later · before 14.14
  • postgresql postgresql15.0 and later · before 15.9
  • postgresql postgresql16.0 and later · before 16.5
  • postgresql postgresql17.0

Versions reported by the vendor

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

  • n/a PostgreSQL

    • 17 and later · before 17.1affected · rpm
    • 16 and later · before 16.5affected · rpm
    • 15 and later · before 15.9affected · rpm
    • 14 and later · before 14.14affected · rpm
    • 13 and later · before 13.17affected · rpm
    • before 12.21affected · rpm

Package-level exposure

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

EcosystemPackageAffected rangeFix
Alpine:v3.17postgresql13before 13.17-r013.17-r0
Alpine:v3.17postgresql14before 14.14-r014.14-r0
Alpine:v3.17postgresql15before 15.9-r015.9-r0
Alpine:v3.19postgresql16before 16.5-r016.5-r0
Alpine:v3.21postgresql17before 17.1-r017.1-r0
Debian:11postgresql-13before 13.17-0+deb11u113.17-0+deb11u1
Debian:12postgresql-15before 15.9-0+deb12u115.9-0+deb12u1
Debian:13postgresql-17before 17.1-117.1-1
openSUSE:Leap 15.5postgresqlbefore 17-150500.10.9.117-150500.10.9.1
openSUSE:Leap 15.5postgresql12before 12.22-150200.8.66.112.22-150200.8.66.1
openSUSE:Leap 15.5postgresql13before 13.18-150200.5.64.113.18-150200.5.64.1
openSUSE:Leap 15.5postgresql14before 14.15-150200.5.50.114.15-150200.5.50.1
openSUSE:Leap 15.5postgresql15before 15.10-150200.5.33.115.10-150200.5.33.1
openSUSE:Leap 15.5postgresql16before 16.6-150200.5.21.116.6-150200.5.21.1
openSUSE:Leap 15.5postgresql17before 17.2-150200.5.5.117.2-150200.5.5.1
openSUSE:Leap 15.6postgresqlbefore 17-150600.17.6.117-150600.17.6.1
openSUSE:Leap 15.6postgresql14before 14.15-150600.16.9.114.15-150600.16.9.1
openSUSE:Leap 15.6postgresql15before 15.10-150600.16.9.115.10-150600.16.9.1
openSUSE:Leap 15.6postgresql16before 16.6-150600.16.10.116.6-150600.16.10.1
openSUSE:Leap 15.6postgresql17before 17.2-150600.13.5.117.2-150600.13.5.1
openSUSE:Tumbleweedpostgresql12before 12.21-1.112.21-1.1
openSUSE:Tumbleweedpostgresql13before 13.17-1.113.17-1.1
openSUSE:Tumbleweedpostgresql14before 14.14-1.114.14-1.1
openSUSE:Tumbleweedpostgresql15before 15.9-1.115.9-1.1

+24

Same product

postgresql: all records

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-2024-7348Aug 8, 2024 · PostgreSQL relation replacement during pg_dump executes arbitrary SQL
    30Monitor
  • ← EarlierCVE-2024-10976Nov 14, 2024 · PostgreSQL row security below e.g. subqueries disregards user ID changes
    21Monitor
  • Later →CVE-2024-10978Nov 14, 2024 · PostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong user ID
    16Monitor

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
n/a PostgreSQL12.21Vendor (CNA)
n/a PostgreSQL13.17Vendor (CNA)
n/a PostgreSQL14.14Vendor (CNA)
n/a PostgreSQL15.9Vendor (CNA)
n/a PostgreSQL16.5Vendor (CNA)
n/a PostgreSQL17.1Vendor (CNA)
azl3 postgresql 16.4-2 on Azure Linux 3.016.5-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 postgresql 16.5-1 on Azure Linux 3.016.5-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 postgresql 14.13-1 on CBL Mariner 2.014.14-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 postgresql 14.13-1 on CBL-Mariner 2.014.14-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 postgresql 14.14-1 on CBL Mariner 2.014.14-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
alpine:postgresql1313.17-r0 · Alpine:v3.17Package registry (OSV)
alpine:postgresql1414.14-r0 · Alpine:v3.17Package registry (OSV)
alpine:postgresql1515.9-r0 · Alpine:v3.17Package registry (OSV)
alpine:postgresql1616.5-r0 · Alpine:v3.19Package registry (OSV)
alpine:postgresql1717.1-r0 · Alpine:v3.21Package registry (OSV)
debian:postgresql-1313.17-0+deb11u1 · Debian:11Package registry (OSV)
debian:postgresql-1515.9-0+deb12u1 · Debian:12Package registry (OSV)
debian:postgresql-1717.1-1 · Debian:13Package registry (OSV)
opensuse:postgresql17-150600.17.6.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:postgresql1212.22-150200.8.66.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:postgresql1313.18-150200.5.64.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:postgresql1414.15-150600.16.9.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:postgresql1515.10-150600.16.9.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:postgresql1616.6-150600.16.10.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:postgresql1717.2-150600.13.5.1 · openSUSE:Leap 15.6Package registry (OSV)
suse:postgresql17-150600.17.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:postgresql1212.22-150200.8.66.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:postgresql1212.22-3.63.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:postgresql1313.18-3.55.2 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)

+6

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.

Credits

All researchers

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

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

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

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

Weakness class (CWE)

CWE-348 · Use of Less Trusted Source

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

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

References

Show all references (1 more)

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

All records