dbcve.org
AutocadApplication · Autodesk

CVE-2023-27912

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 can force an Out-of-Bound Read. A malicious actor can leverage this vulnerability to cause a crash or 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 vulnerability in Autodesk AutoCAD 2023's X_B file parser allows a maliciously crafted X_B file to trigger an out-of-bounds read. This memory access violation can be leveraged by attackers to cause application crashes, read sensitive process memory, or potentially achieve arbitrary code execution within the current process context.

MitigationUsers should avoid opening X_B files from untrusted sources. Organizations should apply Autodesk's security patches for AutoCAD 2023 when released and implement file filtering/validation for X_B file imports at the network perimeter.

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 Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName' in PowerShell to list installed Autodesk products. Look for AutoCAD, Advance Steel, Architecture, Civil 3D, Electrical, LT, Map 3D, or Mechanical.
    Affected if Any of these eight AutoCAD variants are present on the system.
  2. Determine installed version number
    In the Programs and Features list, note the version column for the identified AutoCAD product. Alternatively, launch the AutoCAD application, go to Help > About Autodesk AutoCAD, and record the full version string shown in the license information dialog.
    Affected if A version is displayed that falls within the range 2023.0 through 2023.1.2.
  3. Compare version to vulnerability range
    Parse the version number found in the previous step. The vulnerable range is any version greater than or equal to 2023 but less than 2023.1.3. For example, 2023.0, 2023.1.0, 2023.1.1, and 2023.1.2 are all vulnerable.
    Affected if The installed version is 2023, 2023.1.0, 2023.1.1, or 2023.1.2 (or any 2023.x version below 2023.1.3).
  4. Assess X_B file import exposure
    Check whether users have the ability to import or open X_B files in the installed AutoCAD product. This can be done by attempting to use the INSERT command or checking if X_B is listed in the supported file type filters during the open/import workflow.
    Affected if X_B file import functionality is available and users routinely open files from external or untrusted sources.

The environment is affected if any of the eight AutoCAD 2023 product variants is installed with a version between 2023.0 and 2023.1.2 and users can 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 X_B files from untrusted sources. Organizations should apply Autodesk's security patches for AutoCAD 2023 when released and implement file filtering/validation for X_B file imports at the network perimeter.

Recommended fix High confidence

Autocad 2023.1.3 (or later)

  1. 1. Close any running instances of AutoCAD 2023 or related products (AutoCAD Advance Steel, Architecture, Civil 3D, Electrical, LT, Map 3D, Mechanical)
  2. 2. Ensure all active drawings are saved and closed
  3. 3. Launch the Autodesk Access application or your preferred method for managing Autodesk product updates
  4. 4. Check for available updates for your specific AutoCAD 2023 product
  5. 5. Install the 2023.1.3 update or later version when prompted
  6. 6. Restart your computer if required by the installer
  7. 7. Verify the installed version by opening AutoCAD and checking Help > About AutoCAD to confirm version 2023.1.3 or higher is installed
Caveat Minor version updates typically do not introduce breaking changes; review Autodesk release notes for any specific migration considerations or deprecated features

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

Fix this in Autocad Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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