Memory corruption via revision-history parsing
Published May 17, 2021 · Updated Jul 9, 2026
Heap-based buffer overflow in GNU LibreDWG 0.10 allows remote attackers to corrupt memory through a crafted R2004 DWG file. Public records identify read_2004_section_revhistory at decode.c:3051 but do not disclose the unchecked field or write operation. The public proof of concept requires a user or consuming application to process the file and demonstrates an AddressSanitizer-detected crash.
Summary
What happened
Heap-based buffer overflow in GNU LibreDWG 0.10 allows remote attackers to corrupt memory through a crafted R2004 DWG file. Public records identify read_2004_section_revhistory at decode.c:3051 but do not disclose the unchecked field or write operation. The public proof of concept requires a user or consuming application to process the file and demonstrates an AddressSanitizer-detected crash.
The record
- CVE
- CVE-2020-21842
- Published
- May 17, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- 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
- LibreDWG revision-history parser crash 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