Process crash via unbounded DWG string scan
Published Sep 20, 2021 · Updated Aug 4, 2024
Heap-buffer overread in GNU LibreDWG 0.10.1.3751 and earlier allows attackers to crash DWG-processing programs via a crafted file. During LTYPE decoding, bit_wcs2len scans two-byte code units for a null terminator without limiting the scan to the allocated string buffer. A program must parse the supplied DWG data; the public reproducer demonstrates process termination under AddressSanitizer, with no demonstrated code execution.
Summary
What happened
Heap-buffer overread in GNU LibreDWG 0.10.1.3751 and earlier allows attackers to crash DWG-processing programs via a crafted file. During LTYPE decoding, bit_wcs2len scans two-byte code units for a null terminator without limiting the scan to the allocated string buffer. A program must parse the supplied DWG data; the public reproducer demonstrates process termination under AddressSanitizer, with no demonstrated code execution.
The record
- CVE
- CVE-2021-39522
- Published
- Sep 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 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.
Weakness, pattern, technique
Public exploit references
- heap-buffer-overflow-bit_wcs2len-bits-1634.zipproof 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