Memory corruption via crafted DWG conversion
Published May 17, 2021 · Updated Jul 9, 2026
Heap-based buffer overflow in GNU LibreDWG 0.10.2641 allows local users to corrupt memory by converting a crafted DWG file with dwg2SVG. The public record identifies output_TEXT at dwg2SVG.c line 114 but does not disclose which operation writes beyond the heap allocation. Execution requires a user to supply and convert malicious DWG input; the record does not establish code execution beyond memory corruption or a crash.
Summary
What happened
Heap-based buffer overflow in GNU LibreDWG 0.10.2641 allows local users to corrupt memory by converting a crafted DWG file with dwg2SVG. The public record identifies output_TEXT at dwg2SVG.c line 114 but does not disclose which operation writes beyond the heap allocation. Execution requires a user to supply and convert malicious DWG input; the record does not establish code execution beyond memory corruption or a crash.
The record
- CVE
- CVE-2020-21813
- Published
- May 17, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- 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
- Crafted DWG proof-of-concept fileproof 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