Code execution via TGA parser out-of-bounds write
Published Jun 21, 2022 · Updated Aug 3, 2024
Out-of-bounds write in Autodesk AutoCAD 2023 allows attackers to execute arbitrary code through a maliciously crafted TGA file. The TGA parser writes beyond its allocated buffer while processing attacker-controlled image data. Execution requires a target user to open or otherwise process the file, and resulting code runs in the context of the AutoCAD process.
Summary
What happened
Out-of-bounds write in Autodesk AutoCAD 2023 allows attackers to execute arbitrary code through a maliciously crafted TGA file. The TGA parser writes beyond its allocated buffer while processing attacker-controlled image data. Execution requires a target user to open or otherwise process the file, and resulting code runs in the context of the AutoCAD process.
The record
- CVE
- CVE-2022-27870
- Published
- Jun 21, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 21, 2022CVE 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.
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