Microsoft security update for CVE-2024-10977
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-10977. This page also shows what EchelonGraph holds for CVE-2024-10977, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products5
- azl3 postgresql 16.4-2 on Azure Linux 3.0
- azl3 postgresql 16.5-1 on Azure Linux 3.0
- cbl2 postgresql 14.13-1 on CBL Mariner 2.0
- cbl2 postgresql 14.13-1 on CBL-Mariner 2.0
- cbl2 postgresql 14.14-1 on CBL Mariner 2.0
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 14.14-1 |
| — | Security Update | 16.5-1 |
🧭 EchelonGraph on CVE-2024-10977
- EchelonGraph score
- 3.1 LOW
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
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.
Published by PostgreSQL, the CVE Numbering Authority that assigned CVE-2024-10977, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).