dbcve.org
Subassembly ComposerApplication · Autodesk

CVE-2022-41301

HIGH · 7.8 CVSS v3.1 Published 2022-10-03
Fix available
A fix is available. Upgrade to 2020.6.3 / 2021.3.2 or later.
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 · moderate confidence

SubassemblyComposer.exe contains a memory corruption vulnerability when parsing maliciously crafted PKT files, triggering a read access violation. This vulnerability can potentially be weaponized with other flaws to achieve arbitrary code execution within the application's process context.

MitigationAvoid opening PKT files from untrusted sources; implement strict input validation and bounds checking in the PKT file parser to prevent out-of-bounds memory reads.

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, < 2020.6.3>= 2021, < 2021.3.2>= 2022, < 2022.2.1>= 2023, < 2023.1

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. Confirm Autodesk Subassembly Composer is installed
    Locate SubassemblyComposer.exe on the system, typically found in the Autodesk Subassembly Composer installation directory or via Programs and Features
    Affected if The executable exists on the system
  2. Identify the installed version number
    Right-click SubassemblyComposer.exe, select Properties, and view the File Version field; alternatively, check the application's About or Help > About menu
    Affected if Version cannot be determined or is within an affected release branch
  3. Compare version against affected ranges
    Match the installed version (major.year) to the following vulnerable ranges: 2020 versions prior to 2020.6.3; 2021 versions prior to 2021.3.2; 2022 versions prior to 2022.2.1; 2023 versions prior to 2023.1
    Affected if Installed version falls into any of these ranges: >=2020 <2020.6.3, >=2021 <2021.3.2, >=2022 <2022.2.1, or >=2023 <2023.1
  4. Determine PKT file processing exposure
    Check if the application has been used to open or import PKT files, or if PKT files are stored in accessible locations on the system
    Affected if PKT files have been opened with this application or reside in user-accessible directories

A user is affected if Autodesk Subassembly Composer is installed with a version matching the affected ranges AND PKT files can be processed by the vulnerable executable.

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
Upgrade available Upgrade to 2020.6.3 / 2021.3.2 / 2022.2.1 or later
Fixed in 2020.6.32021.3.22022.2.1
Interim mitigation

Avoid opening PKT files from untrusted sources; implement strict input validation and bounds checking in the PKT file parser to prevent out-of-bounds memory reads.

Recommended fix High confidence

Subassembly Composer 2023.1 (or version 2022.2.1/2021.3.2/2020.6.3 depending on your product line)

  1. Identify the currently installed Subassembly Composer version (2020, 2021, 2022, or 2023 line)
  2. Navigate to the Autodesk Subassembly Composer download page or Autodesk Account portal
  3. Download the latest version corresponding to your product line: 2020.6.3 or later, 2021.3.2 or later, 2022.2.1 or later, or 2023.1 or later
  4. Install the updated Subassembly Composer version
  5. Restart any running instances of Subassembly Composer

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

Fix this in Subassembly Composer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41301 — 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-41301 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