dbcve.org
Advance SteelApplication · Autodesk

CVE-2021-40158

HIGH · 7.8 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to 2022.1.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 JT file in Autodesk Inventor 2022, 2021, 2020, 2019 and AutoCAD 2022 may be forced to read beyond allocated boundaries when parsing the JT file. 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

Out-of-bounds read vulnerability in the JT file parser of Autodesk Inventor 2019-2022 and AutoCAD 2022 allows a maliciously crafted JT file to read beyond allocated memory boundaries. This information disclosure can potentially be chained with other vulnerabilities to achieve code execution in the current process context.

MitigationApply available security patches from Autodesk for the affected product versions. Consider input validation on JT files or disabling JT file handling if not required in the environment.

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
Advance SteelApplication
Affected:>= 2022, < 2022.1.2
AutocadApplication
Affected:>= 2022, < 2022.1.2
Autocad ArchitectureApplication
Affected:>= 2022, < 2022.1.2
Autocad ElectricalApplication
Affected:>= 2022, < 2022.1.2
Autocad LtApplication
Affected:>= 2022, < 2022.1.2
Autocad Map 3dApplication
Affected:>= 2022, < 2022.1.2
Autocad MechanicalApplication
Affected:>= 2022, < 2022.1.2
Autocad MepApplication
Affected:>= 2022, < 2022.1.2

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. Identify installed Autodesk product
    Open the application and go to Help > About, or check Programs and Features in Control Panel to see which Autodesk product is installed (AutoCAD 2022, AutoCAD Architecture 2022, AutoCAD Electrical 2022, AutoCAD LT 2022, AutoCAD Map 3D 2022, AutoCAD Mechanical 2022, AutoCAD MEP 2022, or Advance Steel 2022)
    Affected if Any of the listed products from the affected products list is installed
  2. Check installed version number
    In the application, type the command 'ABOUT' or 'VER' in the command line to display the exact version and build number. Alternatively, right-click the application shortcut, select Properties, and check the version in the Details tab
    Affected if The displayed version is 2022.0.0 through 2022.1.1 (any version >= 2022 but < 2022.1.2)
  3. Confirm JT file handling is active
    Attempt to open or import a JT file (.jt extension) in the application, or check the application settings under Options > File Locations > Support File Search Path to see if JT import paths are defined. JT file support is typically available through the 'ACAD:JT' or similar file extension handler
    Affected if JT file import or handling capability is available and enabled in the application settings

You are affected if you have any of the listed Autodesk products installed with version 2022 through 2022.1.1 and JT file handling functionality is enabled.

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 2022.1.2 or later
Fixed in 2022.1.2
Interim mitigation

Apply available security patches from Autodesk for the affected product versions. Consider input validation on JT files or disabling JT file handling if not required in the environment.

Recommended fix High confidence

2022.1.2

  1. Identify the specific Autodesk product installed (Advance Steel 2022, AutoCAD 2022, AutoCAD Architecture 2022, AutoCAD Electrical 2022, AutoCAD LT 2022, AutoCAD Map 3D 2022, AutoCAD Mechanical 2022, or AutoCAD MEP 2022)
  2. Check the current version to confirm it is less than 2022.1.2 (Help > About > Product Information)
  3. Backup any critical drawings or files created with the affected software
  4. Download the fixed version (2022.1.2 or later) from the Autodesk website or your Autodesk account
  5. Uninstall the current affected version if required by the installer, or install the update over the existing installation
  6. Restart the application and verify the version shows 2022.1.2 or later
Caveat Standard upgrade risk - backup data before upgrading; verify compatibility with custom scripts/plugins

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

Fix this in Advance Steel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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