dbcve.org
AutocadApplication · Autodesk

CVE-2023-27915

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 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 · high confidence

A memory corruption vulnerability in Autodesk AutoCAD 2023 occurs when parsing maliciously crafted X_B files, leading to read access violation. This can be chained with other vulnerabilities to achieve code execution in the current process context.

MitigationApply the vendor-supplied patch for AutoCAD 2023. Until patched, exercise caution when opening X_B files from untrusted sources and consider disabling X_B file handling or running AutoCAD in an isolated 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
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 and version
    Open AutoCAD and go to Help > About Autodesk AutoCAD, or run the command 'ABOUT' in the command line. Note the full version number including the build number.
    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, and the version is 2023.x through 2023.1.2 (any build below 2023.1.3).
  2. Compare version against affected range
    Locate the exact version/build number from the About dialog or registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\AutoCAD\RXX.X (where XX.X is the release year). Compare against the vendor fixed version 2023.1.3.
    Affected if The installed version is 2023, 2023.0.x, 2023.1.0, 2023.1.1, or 2023.1.2 (any version >= 2023 but < 2023.1.3).
  3. Verify X_B file handling is active
    Check the Windows registry under HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\RXX.X\Recent Files for .x_b entries, or inspect recent documents folder for X_B files opened around the time of suspected exploitation.
    Affected if X_B file handling is enabled and the system has recently processed X_B files, especially from untrusted sources.

The environment is affected if any AutoCAD 2023 variant is installed with a version lower than 2023.1.3 and X_B file handling is active.

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

Apply the vendor-supplied patch for AutoCAD 2023. Until patched, exercise caution when opening X_B files from untrusted sources and consider disabling X_B file handling or running AutoCAD in an isolated environment.

Recommended fix High confidence

AutoCAD 2023.1.3 (or subsequent latest stable release)

  1. Navigate to the official Autodesk support website or Autodesk Account portal
  2. Locate the AutoCAD 2023.1.3 update or the latest available stable release for your specific AutoCAD product variant
  3. Download the update installer for your product (AutoCAD, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD Advance Steel, AutoCAD LT, AutoCAD Map 3D, or AutoCAD Mechanical)
  4. Run the installer and follow the on-screen prompts to apply the update
  5. After installation, verify the version by typing "VER" or "ABOUT" in the AutoCAD command line to confirm version 2023.1.3 or later is installed

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-2023-27915 — 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-27915 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