Application interruption via crafted DWG memory leak
Published May 17, 2021 · Updated Jul 9, 2026
Memory leak in dwg_decode_eed in GNU LibreDWG 0.10 allows remote attackers to exhaust process memory through a crafted DWG file opened by a user. The function retains allocated memory while decoding malformed extended entity data instead of releasing it after use. Repeated processing can deplete memory and interrupt the application, without reported confidentiality or integrity impact.
Summary
What happened
Memory leak in dwg_decode_eed in GNU LibreDWG 0.10 allows remote attackers to exhaust process memory through a crafted DWG file opened by a user. The function retains allocated memory while decoding malformed extended entity data instead of releasing it after use. Repeated processing can deplete memory and interrupt the application, without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2020-21839
- Published
- May 17, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- 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.
Weakness, pattern, technique
Public exploit references
- LibreDWG issue 188 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