CVE-2022-41305
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA maliciously crafted PKT file when consumed through SubassemblyComposer.exe application could lead to memory corruption vulnerability by write access violation. This vulnerability in conjunction with other vulnerabilities could lead to code execution in the context of the current process.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA memory corruption vulnerability exists in SubassemblyComposer.exe where parsing a maliciously crafted PKT file leads to a write access violation. This indicates insufficient bounds checking and input validation during PKT file parsing, allowing an attacker to overwrite memory beyond allocated buffers and potentially achieve code execution within the application's process context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2020= 2021= 2022= 2023CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate SubassemblyComposer.exe installationSearch for SubassemblyComposer.exe in typical installation paths such as C:\Program Files\Autodesk\Subassembly Composer\ or check via Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\SubassemblyComposerAffected if The executable exists on the system and version matches 2020, 2021, 2022, or 2023
-
Determine installed product versionRight-click SubassemblyComposer.exe, select Properties, and view the File Version field under the Details tab, or run 'SubassemblyComposer.exe /?' if version is printed to consoleAffected if File version equals 2020.x, 2021.x, 2022.x, or 2023.x
-
Check for recent PKT file activitySearch the file system for .pkt files, particularly in recent project folders, or check application recent files if accessible through the GUIAffected if PKT files have been opened or created using the affected Subassembly Composer version
-
Verify PKT file parsing functionalityOpen any PKT file in Subassembly Composer and observe if the application parses and loads the file without crashingAffected if The application successfully parses PKT files, indicating the vulnerable code path is reachable
The environment is affected if Autodesk Subassembly Composer version 2020, 2021, 2022, or 2023 is installed and PKT files are being parsed by the application.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImplement rigorous input validation and bounds checking on all PKT file parsing routines, including validating file structure, field sizes, and array indices before memory operations; consider replacing unsafe memory functions with safer alternatives and adding exception handling around file parsing code.
Subassembly Composer 2024 or later (latest available version)
- Identify the current Subassembly Composer version installed by opening the application and checking 'About' or the Help menu
- Navigate to the Autodesk Account or Autodesk Support website to download the latest version
- Download and install the most recent Subassembly Composer release (2024 or later)
- Verify the installation completed successfully
- Test that legitimate PKT files open and function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41305 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41305 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data