JLSEC-2026-48
- Source
- https://github.com/JuliaLang/SecurityAdvisories.jl/blob/main/advisories/published/2026/JLSEC-2026-48.md
- Import Source
- https://github.com/JuliaLang/SecurityAdvisories.jl/tree/generated/osv/2026/JLSEC-2026-48.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/JLSEC-2026-48
- Upstream
- Published
- 2026-04-03T13:27:15.647Z
- Modified
- 2026-04-03T13:31:14.941584Z
- Summary
- [none]
- Details
-
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.
- Database specific
{ "license": "CC-BY-4.0", "sources": [ { "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2024-10977", "html_url": "https://nvd.nist.gov/vuln/detail/CVE-2024-10977", "imported": "2026-04-03T13:13:10.621Z", "published": "2024-11-14T13:15:04.023Z", "modified": "2025-11-03T22:16:36.810Z", "id": "CVE-2024-10977" } ] }- References