dbcve.org
AutocadApplication · Autodesk

CVE-2023-29067

HIGH · 7.8 CVSS v3.1 Published 2023-04-14
Fix available
A fix is available. Upgrade to 2023.1.3 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 X_B file when parsed through Autodesk® AutoCAD® 2023 could lead to memory corruption vulnerability by write 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 maliciously crafted X_B file parsed by Autodesk AutoCAD 2023 triggers a memory corruption vulnerability via write access violation. This occurs during the file parsing process, allowing an attacker to overwrite memory regions. When chained with other vulnerabilities, this could enable code execution within the context of the running process.

MitigationUsers should avoid opening untrusted or unsolicited X_B files from unknown sources. Apply vendor-provided security patches for AutoCAD 2023 when released.

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:>= 2023, < 2023.1.3
Autocad Advance SteelApplication
Affected:>= 2023, < 2023.1.3
Autocad ArchitectureApplication
Affected:>= 2023, < 2023.1.3
Autocad Civil 3dApplication
Affected:>= 2023, < 2023.1.3
Autocad ElectricalApplication
Affected:>= 2023, < 2023.1.3
Autocad LtApplication
Affected:>= 2023, < 2023.1.3
Autocad Map 3dApplication
Affected:>= 2023, < 2023.1.3
Autocad MechanicalApplication
Affected:>= 2023, < 2023.1.3

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 AutoCAD product variant
    Open AutoCAD and check the product name in the About dialog (type ABOUT at command line) or look in Help > About Autodesk AutoCAD
    Affected if The product is one of: AutoCAD, AutoCAD Advance Steel, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, or AutoCAD Mechanical
  2. Determine installed version number
    In AutoCAD, type VER or INFO at the command line, or check Help > About Autodesk AutoCAD to see the full version string (for example, 2023.1.2 or 2023.1.3)
    Affected if The version is 2023.0 through 2023.1.2 (any version >= 2023 but < 2023.1.3)
  3. Verify X_B file handling capability
    Attempt to open or import a file with .X_B extension using the OPEN, IMPORT, or XREF command in AutoCAD
    Affected if X_B file parsing is available and the software accepts X_B files for processing

You are affected if you have any AutoCAD 2023 product variant installed with a version between 2023.0 and 2023.1.2 inclusive, and you can open or import X_B 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.3 or later
Fixed in 2023.1.3
Interim mitigation

Users should avoid opening untrusted or unsolicited X_B files from unknown sources. Apply vendor-provided security patches for AutoCAD 2023 when released.

Recommended fix High confidence

AutoCAD 2023.1.3 or later

  1. Identify current AutoCAD version by clicking Help > About AutoCAD
  2. Navigate to Autodesk Account or use the in-app update checker to obtain AutoCAD 2023.1.3 or later
  3. Download the update package for your specific AutoCAD variant (AutoCAD, AutoCAD Advance Steel, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, or AutoCAD Mechanical)
  4. Close all AutoCAD instances and any related Autodesk processes
  5. Run the installer with administrative privileges and follow the on-screen prompts
  6. Restart AutoCAD and verify the version shows 2023.1.3 or later under Help > About
Caveat Review Autodesk release notes for 2023.1.3 for any product-specific changes or known issues before deploying

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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