Crash via fixed-length APPINFO heap over-read
Published Sep 20, 2021 · Updated Aug 4, 2024
Heap-buffer over-read in GNU LibreDWG 0.10.1.3751 and earlier allows attackers to crash DWG-processing applications via a crafted DWG file. The appinfo_private function passes a six-byte heap string to memcmp with a fixed 12-byte comparison length, causing an out-of-bounds read. Exploitation requires a user or application to process the malicious file; the demonstrated consequence is an AddressSanitizer abort.
Summary
What happened
Heap-buffer over-read in GNU LibreDWG 0.10.1.3751 and earlier allows attackers to crash DWG-processing applications via a crafted DWG file. The appinfo_private function passes a six-byte heap string to memcmp with a fixed 12-byte comparison length, causing an out-of-bounds read. Exploitation requires a user or application to process the malicious file; the demonstrated consequence is an AddressSanitizer abort.
The record
- CVE
- CVE-2021-39527
- Published
- Sep 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2021CVE 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
- heap-buffer-overflow-appinfo_private-decode-2993.zipproof 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