Application crash via unchecked DWG page copy
Published May 18, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in GNU LibreDWG 0.10.1 allows attackers to crash applications by supplying a crafted DWG file. The read_system_page function copies size_uncomp bytes from pedata without verifying that the decoded heap buffer contains that many bytes, causing an out-of-bounds read. A victim must process a crafted R2007 DWG file; the demonstrated outcome is an AddressSanitizer abort and service interruption, not data disclosure or modification.
Summary
What happened
Heap-based buffer overflow in GNU LibreDWG 0.10.1 allows attackers to crash applications by supplying a crafted DWG file. The read_system_page function copies size_uncomp bytes from pedata without verifying that the decoded heap buffer contains that many bytes, causing an out-of-bounds read. A victim must process a crafted R2007 DWG file; the demonstrated outcome is an AddressSanitizer abort and service interruption, not data disclosure or modification.
The record
- CVE
- CVE-2020-23861
- Published
- May 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 18, 2021CVE 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 read_system_page heap-overflow 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