Memory corruption via htmlescape off-by-one writes
Published May 17, 2021 · Updated Jul 9, 2026
Heap buffer overflow in GNU LibreDWG 0.10.2641 allows context-dependent attackers to corrupt memory via a crafted DWG file. The dwg2SVG htmlescape routine in programs/escape.c performs off-by-one writes while escaping text from the input file, overrunning its heap allocation. A user or consuming application must process the crafted file; the published reproducer triggers the fault under AddressSanitizer, while code execution has not been demonstrated.
Summary
What happened
Heap buffer overflow in GNU LibreDWG 0.10.2641 allows context-dependent attackers to corrupt memory via a crafted DWG file. The dwg2SVG htmlescape routine in programs/escape.c performs off-by-one writes while escaping text from the input file, overrunning its heap allocation. A user or consuming application must process the crafted file; the published reproducer triggers the fault under AddressSanitizer, while code execution has not been demonstrated.
The record
- CVE
- CVE-2020-21818
- 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
- htmlescape crafted 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