CVE-2023-41140
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 PRT file when parsed through Autodesk AutoCAD 2024 and 2023 can be used to cause a Heap-Based Buffer Overflow. 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 · high confidenceA heap-based buffer overflow vulnerability in Autodesk AutoCAD 2023 and 2024 allows remote code execution when parsing maliciously crafted PRT (plotter) files. The vulnerability permits an attacker to crash the application, read sensitive data, or execute arbitrary code within the current process context.
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< 2024.1>= 2023.0.0, < 2023.1.4>= 2024.0.0, < 2024.1.1< 2023.1.4>= 2024.0.0, < 2024.1.1< 2023.1.4>= 2024.0.0, < 2024.1.1< 2023.1.4>= 2024.0.0, < 2024.1.1< 2023.1.4>= 2024.0.0, < 2024.1.1< 2023.1.4< 2024.1>= 2024.0.0, < 2024.1.1< 2023.1.4>= 2024.0.0, < 2024.1.1< 2023.1.4>= 2024.0.0, < 2024.1.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed AutoCAD product and versionOpen AutoCAD, click the Application menu, then click About. The version number appears in the splash screen or About dialog. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Autodesk\AutoCAD\ for the installed version key.Affected if The installed version falls within any of these ranges: 2023.0.0 to 2023.1.3, or 2024.0.0 to 2024.1.0 (or < 2024.1 for certain product variants).
-
Determine the specific AutoCAD variantCheck whether the installation is base AutoCAD or a vertical product (Advance Steel, Architecture, Civil 3D, Electrical, LT, Map 3D, or Mechanical). This can be identified in the About dialog or the installed program name in Programs and Features.Affected if The variant matches one of the affected products listed in the CVE and the version is in the vulnerable range.
-
Confirm PRT file handling capabilityVerify that the AutoCAD installation includes plotter configuration support, which enables PRT file parsing. This is a standard feature in default AutoCAD installations used for plotter and printer configuration.Affected if The installation can open, import, or configure PRT (plotter) files. This is enabled by default in standard AutoCAD installations.
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.42024.12024.1.1
Apply the vendor-supplied security patch from Autodesk to all affected AutoCAD 2023 and 2024 installations.
Upgrade to AutoCAD 2023.1.4 or later, or 2024.1.1 or later (depending on your product line)
- 1. Verify the current installed version of AutoCAD or affected product variant by opening the application, clicking the 'About' button (typically found in the Help menu), or checking 'Add or Remove Programs' in Windows Control Panel.
- 2. Close all running Autodesk applications completely before proceeding with the update.
- 3. Launch the Autodesk AutoCAD or affected product variant.
- 4. Navigate to the 'Manage' tab in the ribbon interface.
- 5. Click on 'Updates and Add-ons' or check for updates within the application.
- 6. Alternatively, download the update directly from the Autodesk Account portal at accounts.autodesk.com, then go to 'Products and Services' > 'All Products' and locate your product.
- 7. Download and install the appropriate update: For 2023.x versions, install update 2023.1.4 or later; For 2024.x versions, install update 2024.1.1 or later.
- 8. Restart the application after the update completes.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41140 — 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-41140 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