Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-10977 | First vendor Publication | 2024-11-14 |
Vendor | Cve | Last vendor Modification | 2025-02-20 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | |||
---|---|---|---|
Overall CVSS Score | 3.7 | ||
Base Score | 3.7 | Environmental Score | 3.7 |
impact SubScore | 1.4 | Temporal Score | 3.7 |
Exploitabality Sub Score | 2.2 | ||
Attack Vector | Network | Attack Complexity | High |
Privileges Required | None | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | None |
Integrity Impact | Low | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
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. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-10977 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-345 | Insufficient Verification of Data Authenticity |
CPE : Common Platform Enumeration
Sources (Detail)
Source | Url |
---|
Alert History
Date | Informations |
---|---|
2025-02-20 21:20:35 |
|
2024-11-15 17:20:30 |
|
2024-11-14 17:20:27 |
|