CVE-2023-29075
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 an Out-Of-Bounds Write. 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 crafted PRT (part file) parsed by AutoCAD 2023 or 2024 triggers an out-of-bounds memory write vulnerability. An attacker can exploit this by tricking a user into opening the malicious file, potentially achieving arbitrary code execution in the context of the user's AutoCAD 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< 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 productOpen AutoCAD and go to Help > About AutoCAD, or check Programs and Features in Control Panel for installed Autodesk productsAffected if Any AutoCAD 2023 or 2024 variant is installed (including verticals like Architecture, Civil 3D, Electrical, Mechanical, Advance Steel, LT, Map 3D)
-
Determine installed version numberIn AutoCAD, type VER or VERIFY at the command line, or check the version in Help > About AutoCAD. Compare against: 2023 versions < 2023.1.4, or 2024 versions < 2024.1.1Affected if The installed version is 2023.0.0 through 2023.1.3, or 2024.0.0 through 2024.1.0
-
Verify .PRT file handling is activeCheck if PRT file association exists in Windows: go to Settings > Apps > Default Apps > Choose defaults by file type, or look for .prt in File Explorer > View > Options > File AssociationsAffected if PRT files are associated with AutoCAD and can be opened directly by double-clicking
-
Inspect recent PRT file activityCheck the recent documents folder or Windows Jump List for recently opened .PRT files, or review the drawing pool in working directories for any untrusted PRT filesAffected if User has opened or may open untrusted PRT files from unknown sources
If AutoCAD 2023 version < 2023.1.4 or 2024 version < 2024.1.1 is installed and the system handles .PRT files, the environment is vulnerable to this attack vector.
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 patch from Autodesk for AutoCAD 2023 and 2024 when available. Until then, avoid opening untrusted PRT files from unknown sources and consider restricting file handling permissions.
AutoCAD 2023.1.4 or later; AutoCAD 2024.1.1 or later (or AutoCAD 2024.1+ for older versions)
- 1. Determine the current installed version of AutoCAD or the affected product by opening the application and navigating to Help > About AutoCAD (or equivalent for the specific product).
- 2. For AutoCAD 2023.x versions: Upgrade to version 2023.1.4 or later.
- 3. For AutoCAD 2024.x versions: Upgrade to version 2024.1.1 or later.
- 4. For older versions of AutoCAD (pre-2023): Upgrade to AutoCAD 2024.1 or later.
- 5. Download the updated version from the official Autodesk website (www.autodesk.com) under your account's software downloads section.
- 6. Ensure all users with access to the affected software apply the update.
- 7. After upgrading, verify the version by checking Help > About to confirm the fix is applied.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29075 — 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-29075 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