Memory corruption via unsafe DWG sentinel scan
Published May 17, 2021 · Updated Jul 9, 2026
Heap-buffer overflow in GNU LibreDWG 0.10 allows remote attackers to corrupt memory by inducing a user to process a crafted DWG file. The fault is reached as bit_search_sentinel compares input bytes with a 16-byte DWG sentinel; the upstream report does not disclose the corrupting write or faulty bound. User interaction is required; the published proof of concept demonstrates an AddressSanitizer-detected failure, while reliable code execution is not established.
Summary
What happened
Heap-buffer overflow in GNU LibreDWG 0.10 allows remote attackers to corrupt memory by inducing a user to process a crafted DWG file. The fault is reached as bit_search_sentinel compares input bytes with a 16-byte DWG sentinel; the upstream report does not disclose the corrupting write or faulty bound. User interaction is required; the published proof of concept demonstrates an AddressSanitizer-detected failure, while reliable code execution is not established.
The record
- CVE
- CVE-2020-21840
- Published
- May 17, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 17, 2021CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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
- Fuzz-generated 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