Process crash via malformed owned-entity reference
Published Jan 8, 2020 · Updated Aug 4, 2024
NULL pointer dereference in GNU LibreDWG 0.9.3.2564 allows attackers to crash a consuming process with a crafted DWG file. While decoded drawing objects are traversed, get_next_owned_entity in dwg.c dereferences a null object pointer instead of rejecting the malformed state. Processing attacker-supplied DWG content and user interaction are required; the documented consequence is a process crash without confidentiality or integrity impact.
Summary
What happened
NULL pointer dereference in GNU LibreDWG 0.9.3.2564 allows attackers to crash a consuming process with a crafted DWG file. While decoded drawing objects are traversed, get_next_owned_entity in dwg.c dereferences a null object pointer instead of rejecting the malformed state. Processing attacker-supplied DWG content and user interaction are required; the documented consequence is a process crash without confidentiality or integrity impact.
The record
- CVE
- CVE-2020-6611
- Published
- Jan 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- Crafted DWG crash 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