Process crash via fixed-length section-name copy
Published Nov 30, 2022 · Updated Apr 24, 2025
Heap buffer overflow in LibreDWG 0.12.4.4643 allows context-dependent attackers to crash DWG-processing applications via a crafted pre-R13 file. The decode_preR13_section_hdr routine uses strncpy to copy 63 bytes while parsing the section header, producing an out-of-bounds heap write. A user or consuming application must process the file; the published proof demonstrates process termination but not code execution.
Summary
What happened
Heap buffer overflow in LibreDWG 0.12.4.4643 allows context-dependent attackers to crash DWG-processing applications via a crafted pre-R13 file. The decode_preR13_section_hdr routine uses strncpy to copy 63 bytes while parsing the section header, producing an out-of-bounds heap write. A user or consuming application must process the file; the published proof demonstrates process termination but not code execution.
The record
- CVE
- CVE-2022-45332
- Published
- Nov 30, 2022
- Updated
- Apr 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 30, 2022CVE publishedPublication date reported by the CVE source.
- Apr 24, 2025Record 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 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