Application crash via unchecked compressed-section memcpy
Published May 17, 2021 · Updated Jul 9, 2026
Heap-based buffer overflow in GNU LibreDWG 0.10 allows attackers to crash a consuming application with a crafted DWG file. During R2004 compressed-section parsing, read_2004_compressed_section passes an unchecked section size to memcpy, writing past the allocated decompression buffer. Processing the file is required, and the demonstrated consequence is an AddressSanitizer-detected crash rather than a confirmed code-execution path.
Summary
What happened
Heap-based buffer overflow in GNU LibreDWG 0.10 allows attackers to crash a consuming application with a crafted DWG file. During R2004 compressed-section parsing, read_2004_compressed_section passes an unchecked section size to memcpy, writing past the allocated decompression buffer. Processing the file is required, and the demonstrated consequence is an AddressSanitizer-detected crash rather than a confirmed code-execution path.
The record
- CVE
- CVE-2020-21827
- Published
- May 17, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- 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
- LibreDWG dwg2dxf 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