Process memory corruption via decode_preR13
Published Dec 2, 2021 · Updated Aug 3, 2024
Heap-buffer overflow in LibreDWG 0.12.3 allows attackers to crash or corrupt processes via a crafted DWG file. The decode_preR13 parser writes beyond a heap allocation while decoding malformed pre-R13 sections, as demonstrated by an AddressSanitizer report. Exploitation requires getting the crafted file processed by LibreDWG; the published evidence does not establish remote service exposure or code execution.
Summary
What happened
Heap-buffer overflow in LibreDWG 0.12.3 allows attackers to crash or corrupt processes via a crafted DWG file. The decode_preR13 parser writes beyond a heap allocation while decoding malformed pre-R13 sections, as demonstrated by an AddressSanitizer report. Exploitation requires getting the crafted file processed by LibreDWG; the published evidence does not establish remote service exposure or code execution.
The record
- CVE
- CVE-2021-28237
- Published
- Dec 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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
- poc.zip from LibreDWG issue #325proof 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