CVE-2024-10977
PostgreSQL SSL/TLS Replay Attack Vulnerability
Description
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.
INFO
Published Date :
Nov. 14, 2024, 1:15 p.m.
Last Modified :
Nov. 15, 2024, 1:58 p.m.
Source :
f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
Remotely Exploitable :
Yes !
Impact Score :
1.4
Exploitability Score :
1.6
Affected Products
The following products are affected by CVE-2024-10977
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-10977.
| URL | Resource |
|---|---|
| https://www.postgresql.org/support/security/CVE-2024-10977/ |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-10977 vulnerability anywhere in the article.
-
Cybersecurity News
PostgreSQL Releases Security Update Addressing Multiple Vulnerabilities
The PostgreSQL Global Development Group has issued an important update addressing four security vulnerabilities across all supported versions of the popular open-source database system. This includes ... Read more
The following table lists the changes that have been made to the
CVE-2024-10977 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Received by f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
Nov. 14, 2024
Action Type Old Value New Value Added Description 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. Added Reference PostgreSQL https://www.postgresql.org/support/security/CVE-2024-10977/ [No types assigned] Added CWE PostgreSQL CWE-348 Added CVSS V3.1 PostgreSQL AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-10977 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-10977
weaknesses.