CVE-2024-23145
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 in opennurbs.dll through Autodesk applications, can force an Out-of-Bound Read. 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 · moderate confidenceA maliciously crafted PRT file parsed by the opennurbs.dll library in Autodesk applications triggers an out-of-bounds read vulnerability. This can allow an attacker to cause a denial of service, read sensitive memory contents, or achieve arbitrary code execution within 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>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.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
- 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 Autodesk productsCheck Program Files for Autodesk folders, or open each application and go to Help > About Autodesk [Product] to see the versionAffected if Any of these products are installed: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D
-
Determine exact version of the Autodesk productIn the application, go to Help > About Autodesk [Product] and note the full version number (for example, 2023.1.5)Affected if Version is >= 2022 but < 2022.1.5; OR >= 2023 but < 2023.1.6; OR >= 2024 but < 2024.1.4; OR >= 2025 but < 2025.1
-
Locate the opennurbs.dll fileSearch for opennurbs.dll in the application installation directory, typically under C:\Program Files\Autodesk\[Product]\[Version]\Affected if The DLL exists in the product folder, confirming the component is present
-
Check if PRT file handling is usedReview whether the user or workflow involves opening or importing PRT files in the Autodesk applicationAffected if PRT files are processed or could be opened by the user in the application
A user is affected if they have any of the listed Autodesk products installed with a version falling within the affected ranges and they process PRT files.
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 · scoped2022.1.52023.1.62024.1.4
Restrict processing of untrusted PRT files and apply the vendor patch when available; avoid opening PRT files from untrusted or unverified sources until the fix is deployed.
Upgrade to AutoCAD 2022.1.5 or later; 2023.1.6 or later; 2024.1.4 or later; or 2025.1 or later (matching your product year)
- Identify the current version of the installed Autodesk application (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D)
- Determine which product year (2022, 2023, 2024, or 2025) is installed
- For AutoCAD 2022: Upgrade to version 2022.1.5 or later
- For AutoCAD 2023: Upgrade to version 2023.1.6 or later
- For AutoCAD 2024: Upgrade to version 2024.1.4 or later
- For AutoCAD 2025: Upgrade to version 2025.1 or later
- For other affected products (Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, Civil 3D): Apply the same version threshold based on their product year
- Download the update from the official Autodesk website (www.autodesk.com) or use the Autodesk Access application to check for updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23145 — 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-2024-23145 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