Application crash via page-map buffer over-read
Published Jan 8, 2020 · Updated Aug 4, 2024
Heap-based buffer over-read in GNU LibreDWG 0.9.3.2564 allows context-dependent attackers to crash applications via a crafted DWG file. During page-map parsing, read_pages_map performs an eight-byte read at the end of its allocated system-page buffer. A victim application must parse the file; the published proof of concept demonstrates an AddressSanitizer-detected abort rather than memory disclosure.
Summary
What happened
Heap-based buffer over-read in GNU LibreDWG 0.9.3.2564 allows context-dependent attackers to crash applications via a crafted DWG file. During page-map parsing, read_pages_map performs an eight-byte read at the end of its allocated system-page buffer. A victim application must parse the file; the published proof of concept demonstrates an AddressSanitizer-detected abort rather than memory disclosure.
The record
- CVE
- CVE-2020-6609
- Published
- Jan 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, CAPEC-540
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- LibreDWG crafted DWG proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo