dbcve.org
Subassembly ComposerApplication · Autodesk

CVE-2022-41308

HIGH · 7.8 CVSS v3.1 Published 2022-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A maliciously crafted PKT file when consumed through SubassemblyComposer.exe application could lead to memory corruption vulnerability by read 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 confidence

A memory corruption vulnerability exists in SubassemblyComposer's PKT file parser where a maliciously crafted file triggers a read access violation. The vulnerability allows an attacker to corrupt memory through the parsing process, potentially enabling code execution when combined with other exploitation primitives.

MitigationApply the vendor patch when available; until then, exercise extreme caution with PKT files from untrusted sources and consider running SubassemblyComposer in an isolated environment to limit blast radius.

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
Subassembly ComposerApplication
Affected:= 2020= 2021= 2022= 2023

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Subassembly Composer is installed
    Check for the presence of Autodesk Subassembly Composer on the system. Common installation paths include C:\Program Files\Autodesk\Subassembly Composer or C:\Program Files (x86)\Autodesk\Subassembly Composer. On Windows, you can also check via Add/Remove Programs or the following PowerShell command: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Subassembly Composer*'}
    Affected if Subassembly Composer is not installed on the system, the vulnerability does not apply.
  2. Identify installed version
    Locate the Subassembly Composer executable and check its version properties. In the installation directory, right-click on SubassemblyComposer.exe, select Properties, and view the Details tab for File Version. Alternatively, use PowerShell: Get-ChildItem -Path 'C:\Program Files\Autodesk\Subassembly Composer' -Filter '*.exe' | ForEach-Object { $_.VersionInfo.FileVersion }
    Affected if The installed version matches 2020, 2021, 2022, or 2023, indicating the affected versions.
  3. Confirm PKT file handling capability
    Verify that the PKT file parser module is present and functional. PKT files are Subassembly Package files used by Subassembly Composer. Check for the existence of file association or parsing libraries within the Subassembly Composer installation directory.
    Affected if PKT file parsing functionality is present and the application can open PKT files, making the vulnerability reachable.
  4. Review recent PKT file activity
    Examine recent file access logs or the application's recent files list to determine if PKT files from untrusted sources have been opened. Check Windows Event Viewer for application crash events related to Subassembly Composer, or review the application's recent documents if available.
    Affected if PKT files from untrusted or unknown sources have been opened, there is potential for exploitation.

A user is affected if Autodesk Subassembly Composer versions 2020, 2021, 2022, or 2023 are installed and PKT files are processed, as the vulnerability lies in the PKT file parser component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch when available; until then, exercise extreme caution with PKT files from untrusted sources and consider running SubassemblyComposer in an isolated environment to limit blast radius.

Recommended fix Moderate confidence

Latest Subassembly Composer 2023 or newer release

  1. 1. Navigate to the Autodesk Subassembly Composer download page or Autodesk Account portal.
  2. 2. Check for the latest version of Subassembly Composer that addresses security vulnerabilities.
  3. 3. Download and install the most recent version available.
  4. 4. Verify the installation by checking the application version in the Help > About menu.
Caveat Review Autodesk's release notes for any changes to PKT file handling or workflow modifications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Subassembly Composer Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41308 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41308 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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