Code execution via unchecked PKT decoder write
Published Oct 14, 2022 · Updated May 14, 2025
Out-of-bounds write in Autodesk Subassembly Composer 2020 through 2023 allows attackers to execute code via a crafted PKT file. The PKT decoder fails to enforce a bounds check before writing malformed file data, corrupting memory outside the intended buffer. Exploitation requires the file to be processed locally, and successful code execution runs in the SubassemblyComposer.exe process context.
Summary
What happened
Out-of-bounds write in Autodesk Subassembly Composer 2020 through 2023 allows attackers to execute code via a crafted PKT file. The PKT decoder fails to enforce a bounds check before writing malformed file data, corrupting memory outside the intended buffer. Exploitation requires the file to be processed locally, and successful code execution runs in the SubassemblyComposer.exe process context.
The record
- CVE
- CVE-2022-41308
- Published
- Oct 14, 2022
- Updated
- May 14, 2025
- Vendor
- Autodesk
- Product
- Autodesk Subassembly Composer
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 14, 2022CVE publishedPublication date reported by the CVE source.
- May 14, 2025Record 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=2023, 2022, 2021, 2022
What conditions does exploitation require?
What is affected?
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