CVE-2023-27914
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 · uneditedA maliciously crafted X_B file when parsed through Autodesk® AutoCAD® 2023 can be used to write beyond the allocated buffer causing a Stack Buffer Overflow. 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 confidenceA stack buffer overflow vulnerability exists in Autodesk AutoCAD 2023 when parsing maliciously crafted X_B files. The vulnerability occurs during file parsing when the application writes beyond the allocated buffer on the stack, potentially allowing an attacker to cause crashes, read sensitive data from memory, or execute arbitrary code in the context of the current process.
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>= 2023, < 2023.1.3>= 2023, < 2023.1.3>= 2023, < 2023.1.3>= 2023, < 2023.1.3>= 2023, < 2023.1.3>= 2023, < 2023.1.3>= 2023, < 2023.1.3>= 2023, < 2023.1.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed AutoCAD productOpen the application and go to Help > About, or check the Windows Programs and Features list to find the exact product name and version number installedAffected 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
-
Compare version against affected rangeCheck if the installed version is 2023.x (where x is any update prior to 2023.1.3)Affected if The installed version is 2023, 2023.1, 2023.1.1, or 2023.1.2 (any version >= 2023 but < 2023.1.3)
-
Verify X_B file handling is presentConfirm the installation includes DWG/associative file parsing capabilities - X_B is a legacy format typically supported in standard AutoCAD installationsAffected if The application has standard file import capabilities and can potentially open X_B files (this is built-in to affected versions)
You are affected if you have any of the listed AutoCAD 2023 products installed with a version lower than 2023.1.3.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2023.1.3
Apply the Autodesk security patch for CVE-2023-27914 when available. Until then, avoid opening untrusted X_B files in AutoCAD 2023 and ensure users operate with the minimum privileges necessary.
AutoCAD 2023.1.3 (or later) for all affected variants
- Back up all critical AutoCAD drawings, templates, and user settings before updating
- Navigate to the Autodesk Account or AutoCAD download page at www.autodesk.com
- Download AutoCAD 2023 version 2023.1.3 or later (or the corresponding version for your specific AutoCAD variant)
- Run the installer as an administrator
- Follow the on-screen prompts to complete the installation
- Restart AutoCAD after the update completes
- Verify the installed version by checking Help > About AutoCAD to confirm version 2023.1.3 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-27914 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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