CVE-2024-10977 [Low] | Security Vulnerability in Postgresql

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-01-29	0.38%	0.34%	-0.03%
2	2025-12-23	0.05%	0.38%	+0.32%
3	2025-06-20	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-01-29

0.38%

0.34%

-0.03%

2025-12-23

0.05%

0.38%

+0.32%

2025-06-20

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
3.1	3.1	LOW	`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. 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.	1.6	1.4	f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
3.7	3.1	LOW	`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. 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:N) Doesn’t really leak secrets in a meaningful way. 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.2	1.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

3.1

LOW

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
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.

1.6

1.4

f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

3.7

3.1

LOW

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
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:N): Doesn’t really leak secrets in a meaningful way.
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.2

1.4

[email protected]

OS Trackers for CVE-2024-10977

vendor	priority	summary	link
`alpine`	low	CVE-2024-10977: 5 source package rows (postgresql, postgresql14, postgresql15, postgresql16, postgresql17); 37 state rows across 11 repos (3.17-main, 3.18-main, 3.19-main, 3.20-community, 3.20-main, 3.21-community, 3.21-main, 3.22-community, 3.22-main, edge-community, edge-main); fixed 19, open 18.	https://security.alpinelinux.org/vuln/CVE-2024-10977
`debian`	not yet assigned	CVE-2024-10977 not yet assigned priority: Debian including 3 source packages (postgresql-13, postgresql-15, postgresql-17), 3 status rows across 3 suites (bookworm, bullseye, trixie): resolved 3.	https://security-tracker.debian.org/tracker/CVE-2024-10977
`gentoo`	high	CVE-2024-10977: 1 GLSA(s) (202412-12), 1 atom(s) (dev-db/postgresql); latest impact high.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2024-10977
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2024-10977
`suse`	medium	CVE-2024-10977 severity moderate: SUSE including 653 source package names (0:libpq5-17.2-150600.13.5.1, 15.10-42.1:libpq5-17.2-150200.5.5.1, …), 1707 product×package rows across 53 product lines (Container containers/open-webui, Container private-registry/harbor-db, … (53 product lines)): Fixed 1476, Known Affected 231.	https://www.suse.com/security/cve/CVE-2024-10977/
`ubuntu`	medium	CVE-2024-10977 medium priority: Ubuntu including 8 source packages (postgresql-10, postgresql-12, …), 59 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 42, released 9, ignored 3, needs-triage 2, not-affected 2, deferred 1.	https://ubuntu.com/security/CVE-2024-10977

Affected software / configurations for CVE-2024-10977

Vendor	Product	Version	Raw CPE
postgresql	postgresql	>= 12.0, < 12.21	cpe:2.3:a:postgresql:postgresql::::::::
postgresql	postgresql	>= 13.0, < 13.17	cpe:2.3:a:postgresql:postgresql::::::::
postgresql	postgresql	>= 14.0, < 14.14	cpe:2.3:a:postgresql:postgresql::::::::
postgresql	postgresql	>= 15.0, < 15.9	cpe:2.3:a:postgresql:postgresql::::::::
postgresql	postgresql	>= 16.0, < 16.5	cpe:2.3:a:postgresql:postgresql::::::::
postgresql	postgresql	17.0	cpe:2.3:a:postgresql:postgresql:17.0:-::::::
postgresql	postgresql	17.0	cpe:2.3:a:postgresql:postgresql:17.0:beta1::::::
postgresql	postgresql	17.0	cpe:2.3:a:postgresql:postgresql:17.0:beta2::::::
postgresql	postgresql	17.0	cpe:2.3:a:postgresql:postgresql:17.0:beta3::::::
postgresql	postgresql	17.0	cpe:2.3:a:postgresql:postgresql:17.0:rc1::::::

References for CVE-2024-10977

URL	Tags
https://www.postgresql.org/support/security/CVE-2024-10977/	Vendor Advisory
https://lists.debian.org/debian-lts-announce/2024/11/msg00011.html

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2024-10977

Common vulnerability scoring system (CVSS) metrics for CVE-2024-10977

Weakness enumeration for CVE-2024-10977

OS Trackers for CVE-2024-10977

Affected software / configurations for CVE-2024-10977

References for CVE-2024-10977