Code execution via unchecked DWF buffer copy
Published Nov 14, 2021 · Updated Aug 4, 2024
Stack-based buffer overflow in Open Design Alliance ODA Viewer before 2022.11 allows attackers to execute code via a crafted DWF file. During DWF parsing, the viewer copies user-supplied data into a stack-based buffer without validating its length. Opening the file or visiting a malicious page is required, and successful exploitation runs code in the current process.
Summary
What happened
Stack-based buffer overflow in Open Design Alliance ODA Viewer before 2022.11 allows attackers to execute code via a crafted DWF file. During DWF parsing, the viewer copies user-supplied data into a stack-based buffer without validating its length. Opening the file or visiting a malicious page is required, and successful exploitation runs code in the current process.
The record
- CVE
- CVE-2021-43272
- Published
- Nov 14, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-755, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 14, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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