Service crash via heap overflow in DWG parser
Published May 17, 2021 · Updated Jul 9, 2026
Heap-based buffer overflow in GNU LibreDWG 0.10 allows remote attackers to cause service interruption via a crafted DWG file. The read_2004_section_handles routine decodes R2004 section handles without sufficient bounds validation, permitting writes beyond an allocated heap buffer during malformed-file parsing. The condition requires a user or service to process attacker-supplied DWG content; published evidence demonstrates crashes, while code execution is not established.
Summary
What happened
Heap-based buffer overflow in GNU LibreDWG 0.10 allows remote attackers to cause service interruption via a crafted DWG file. The read_2004_section_handles routine decodes R2004 section handles without sufficient bounds validation, permitting writes beyond an allocated heap buffer during malformed-file parsing. The condition requires a user or service to process attacker-supplied DWG content; published evidence demonstrates crashes, while code execution is not established.
The record
- CVE
- CVE-2020-21831
- Published
- May 17, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-122, 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
No public exploit references are available in this record.
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