Code execution via JT parser out-of-bounds read
Published Jan 25, 2022 · Updated Aug 4, 2024
Out-of-bounds read in Autodesk Inventor 2019 through 2022 allows remote attackers to execute code via a malicious JT file. The JT-file parser reads beyond an allocated buffer when processing crafted data, enabling code execution in the current process. Exploitation requires a user to open the malicious file, and execution inherits the Inventor process context.
Summary
What happened
Out-of-bounds read in Autodesk Inventor 2019 through 2022 allows remote attackers to execute code via a malicious JT file. The JT-file parser reads beyond an allocated buffer when processing crafted data, enabling code execution in the current process. Exploitation requires a user to open the malicious file, and execution inherits the Inventor process context.
The record
- CVE
- CVE-2021-40158
- Published
- Jan 25, 2022
- Updated
- Aug 4, 2024
- Vendor
- Autodesk
- Product
- Inventor
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 25, 2022CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2022, 2021, 2020, 2019
What conditions does exploitation require?
What is affected?
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.
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