CVE-2023-41139
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 STP file when parsed through Autodesk AutoCAD 2024 and 2023 can be used to dereference an untrusted pointer. This vulnerability, along with other vulnerabilities, could lead to code execution in 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 STP file parsed by Autodesk AutoCAD 2023 and 2024 can be used to dereference an untrusted pointer. This vulnerability, when combined with other vulnerabilities, could lead to arbitrary code execution 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< 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 productOpen AutoCAD and go to Help > About Autodesk AutoCAD, or check Programs and Features in Control Panel for installed Autodesk softwareAffected if Any AutoCAD family product (AutoCAD, AutoCAD Architecture, Civil 3D, Electrical, Mechanical, Advance Steel, Map 3D, or LT) is installed
-
Determine installed version numberIn AutoCAD, type 'VER' or 'ABOUT' at the command line to display the version and build numberAffected if Version cannot be determined or shows as unknown
-
Compare version against affected rangesMatch the installed version to these vulnerable ranges: 2023.0.0 through 2023.1.3 (or any version < 2023.1.4); 2024.0.0 through 2024.1.0 (or any version < 2024.1.1 for 2024 products, or < 2024.1 for some products)Affected if Installed version falls within any of the affected ranges listed
-
Verify STP file handling is enabledCheck if the application is configured to automatically open or parse STP files. Look in Options > File > Trusted File Locations, or check file association settings for .stp filesAffected if STP file parsing or automatic opening is enabled and the system processes STP files
The environment is affected if any AutoCAD variant from the 2023 or 2024 product lines is installed with a version matching the affected ranges and STP file parsing is active.
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 security update when released; until then, exercise extreme caution with STP files from untrusted sources and consider disabling automatic file parsing where possible.
AutoCAD 2023.1.4 or later; AutoCAD 2024.1.1 or later (or 2024.1 for AutoCAD LT)
- 1. Identify the specific AutoCAD product and version currently installed from the affected versions list.
- 2. For AutoCAD 2023.x versions (>= 2023.0.0, < 2023.1.4): Upgrade to version 2023.1.4 or later.
- 3. For AutoCAD 2024.x versions (>= 2024.0.0, < 2024.1.1): Upgrade to version 2024.1.1 or later.
- 4. For AutoCAD LT (additional version < 2024.1): Upgrade to version 2024.1 or later.
- 5. Download the updated version from the official Autodesk website or your Autodesk Account portal.
- 6. Install the update following standard Autodesk installation procedures.
- 7. Verify the installed version matches or exceeds the fixed version numbers.
- 8. Re-test any STP file workflows to ensure normal functionality after the update.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41139 — 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-41139 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