dbcve.org
AutocadApplication · Autodesk

CVE-2023-29074

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-23
Fix available
A fix is available. Upgrade to 2023.1.4 / 2024.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 CATPART file when parsed through Autodesk AutoCAD 2024 and 2023 can be used to cause an Out-Of-Bounds Write. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code 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

A maliciously crafted CATPART file parsed by Autodesk AutoCAD 2023 or 2024 triggers an out-of-bounds write vulnerability, allowing an attacker to crash the application, read sensitive memory, or execute arbitrary code in the current process context.

MitigationApply vendor patches from Autodesk when available; until then, enforce strict policies prohibiting the opening of untrusted CATPART files from unknown or external sources.

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:< 2024.1>= 2023.0.0, < 2023.1.4>= 2024.0.0, < 2024.1.1
Autocad Advance SteelApplication
Affected:< 2023.1.4>= 2024.0.0, < 2024.1.1
Autocad ArchitectureApplication
Affected:< 2023.1.4>= 2024.0.0, < 2024.1.1
Autocad Civil 3dApplication
Affected:< 2023.1.4>= 2024.0.0, < 2024.1.1
Autocad ElectricalApplication
Affected:< 2023.1.4>= 2024.0.0, < 2024.1.1
Autocad LtApplication
Affected:< 2023.1.4< 2024.1>= 2024.0.0, < 2024.1.1
Autocad Map 3dApplication
Affected:< 2023.1.4>= 2024.0.0, < 2024.1.1
Autocad MechanicalApplication
Affected:< 2023.1.4>= 2024.0.0, < 2024.1.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 AutoCAD product
    Open the application and go to Help > About Autodesk AutoCAD, or check Add/Remove Programs (Programs and Features) for installed Autodesk products. Look for AutoCAD, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, or AutoCAD Advance Steel.
    Affected if Any of these products are installed on the system.
  2. Determine the installed version
    In AutoCAD, type 'VER' or 'ABOUT' at the command prompt, or check the version displayed in the About dialog. Note the full version number (for example, 2023.0.1, 2023.1.3, 2024.0.2, 2024.1.0).
    Affected if A version number is returned that falls within the affected ranges.
  3. Compare version against CVE-affected ranges
    Check if the installed version matches: 2023.0.0 through 2023.1.3 (less than 2023.1.4), OR 2024.0.0 through 2024.1.0 (less than 2024.1.1). For base AutoCAD and AutoCAD LT, also check for versions less than 2024.1.
    Affected if The installed version is less than 2023.1.4 for 2023.x releases, or less than 2024.1.1 for 2024.x releases.
  4. Verify CATPART file handling capability
    Confirm the application has the ability to import or open CATPART files. Check if CATIA V5 or CATPART file import modules are loaded. In AutoCAD, verify if related plugins or modules for CAD data interchange are present.
    Affected if CATPART file parsing capability exists in the installation (this is the attack vector for this vulnerability).

The environment is affected if an Autodesk product from the list is installed with a version between 2023.0.0 and 2023.1.3 (inclusive), or between 2024.0.0 and 2024.1.0 (inclusive), and the system can process CATPART 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 2023.1.4 / 2024.1 / 2024.1.1 or later
Fixed in 2023.1.42024.12024.1.1
Interim mitigation

Apply vendor patches from Autodesk when available; until then, enforce strict policies prohibiting the opening of untrusted CATPART files from unknown or external sources.

Recommended fix High confidence

AutoCAD 2023.1.4 or later; AutoCAD 2024.1.1 or later (or the latest available release for your product line)

  1. 1. Open Autodesk AutoCAD or your specific AutoCAD-based product (e.g., AutoCAD Civil 3D, AutoCAD Architecture)
  2. 2. Check the current version by typing 'VER' or 'ABOUT' in the command line
  3. 3. Close all Autodesk applications completely
  4. 4. Launch Autodesk Access or open a web browser and navigate to the Autodesk Account portal at manage.autodesk.com
  5. 5. Sign in with your Autodesk account credentials
  6. 6. Go to 'All Products' or 'Products and Services' section
  7. 7. Locate your affected AutoCAD product and click 'Download' for the available update
  8. 8. Download version 2024.1.1 or later (for 2024.x releases) or version 2023.1.4 or later (for 2023.x releases)
Caveat Upgrade may require a current Autodesk subscription; some older custom scripts or third-party plugins may need verification for compatibility with the new version

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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