dbcve.org
AutocadApplication · Autodesk

CVE-2024-23134

HIGH · 7.8 CVSS v3.1 Published 2024-02-22
Fix available
A fix is available. Upgrade to 2021.1.4 / 2022.1.4 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 IGS file in tbb.dll when parsed through Autodesk AutoCAD can be used in user-after-free vulnerability. This vulnerability, along with other vulnerabilities, could lead to code execution in 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 user-after-free vulnerability exists in tbb.dll when Autodesk AutoCAD parses maliciously crafted IGS (Initial Graphics Exchange) files. The vulnerability allows an attacker to achieve code execution in the current process by exploiting the use-after-free condition in memory handling.

MitigationApply the vendor patch from Autodesk when available. Until then, avoid opening IGS files from untrusted sources and consider disabling or restricting IGS file import functionality in AutoCAD deployments.

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
AutocadApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad ArchitectureApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad ElectricalApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad MechanicalApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad MepApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad Plant 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Civil 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Advance SteelApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.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. Identify installed Autodesk product
    Check Programs and Features or C:\Program Files\Autodesk for installed AutoCAD variant (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel)
    Affected if Any of these products are installed
  2. Determine product version number
    Open the installed program, access Help > About Autodesk [Product], or right-click the main executable and view Properties > Details to find the exact version (for example, 2023.0.0)
    Affected if Version matches one of the affected ranges: 2021.x (before 2021.1.4), 2022.x (before 2022.1.4), 2023.x (before 2023.1.5), 2024.x (before 2024.1.3), or 2025.x (before 2025.0.1)
  3. Verify IGS import capability is present
    Launch the product and attempt to access IGS file import: use the IMPORT command or navigate to Insert > Import > IGES file, or check if the IGS file type handler is registered in the system
    Affected if IGS file import functionality exists and can be used to load external IGS files into the product
  4. Confirm tbb.dll is present
    Locate tbb.dll in the product installation directory (typically C:\Program Files\Autodesk\[Product]\) or search for the file on the system
    Affected if The vulnerable tbb.dll library is present in the AutoCAD installation folder

The environment is affected if an Autodesk product from the list is installed with a version falling within the affected ranges and IGS file import functionality is available for parsing IGES/IGS files.

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 2021.1.4 / 2022.1.4 / 2023.1.5 or later
Fixed in 2021.1.42022.1.42023.1.5
Interim mitigation

Apply the vendor patch from Autodesk when available. Until then, avoid opening IGS files from untrusted sources and consider disabling or restricting IGS file import functionality in AutoCAD deployments.

Recommended fix High confidence

Upgrade to version 2021.1.4, 2022.1.4, 2023.1.5, or 2024.1.3 depending on your product line (2021-2024)

  1. 1. Open Autodesk AutoCAD or affected product on your system
  2. 2. Check the current version by typing 'VER' or 'ABOUT' in the command line
  3. 3. Navigate to the Autodesk Account or product download page to obtain the update
  4. 4. Download the appropriate update: For 2021.x upgrade to 2021.1.4, for 2022.x upgrade to 2022.1.4, for 2023.x upgrade to 2023.1.5, for 2024.x upgrade to 2024.1.3
  5. 5. Close all Autodesk applications
  6. 6. Run the installer or apply the update
  7. 7. Restart the application and verify the version shows the patched release
Caveat Standard Autodesk update; review release notes for any workflow changes or deprecated features

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

Fix this in Autocad 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-2024-23134 — 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-2024-23134 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