Code execution via JT parser use-after-free
Published Jun 21, 2022 · Updated Aug 3, 2024
Use-after-free in JT file handling in Autodesk AutoCAD 2019 through 2022 allows attackers to execute code via a crafted JT file. Autodesk identifies JT parsing as the locus but has not published which object is freed or how later processing accesses it. A user must open the malicious file, and successful exploitation executes code in the current AutoCAD process.
Summary
What happened
Use-after-free in JT file handling in Autodesk AutoCAD 2019 through 2022 allows attackers to execute code via a crafted JT file. Autodesk identifies JT parsing as the locus but has not published which object is freed or how later processing accesses it. A user must open the malicious file, and successful exploitation executes code in the current AutoCAD process.
The record
- CVE
- CVE-2022-27867
- Published
- Jun 21, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1203, T1204.002
- 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