CVE-2024-8597
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 in ASMDATAX230A.dll through Autodesk AutoCAD can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to cause a crash, write 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 memory corruption vulnerability exists in ASMDATAX230A.dll when parsing maliciously crafted STP (STEP) files in Autodesk AutoCAD. The vulnerability allows an attacker to cause a crash, write sensitive data to memory, 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>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.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
- 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.
-
Check installed AutoCAD versionOpen AutoCAD and type 'ABOUT' in the command line, or check Add/Remove Programs. Alternatively, locate the installation folder (typically C:\Program Files\Autodesk\AutoCAD 2025\) and right-click the acad.exe file to view Properties > Details for the File Version.Affected if The version listed is 2025.0.0 through 2025.1.0 (any build >= 2025 but < 2025.1.1)
-
Verify vulnerable DLL is presentNavigate to the AutoCAD installation directory (e.g., C:\Program Files\Autodesk\AutoCAD 2025\) and locate ASMDATAX230A.dll. Use Windows Explorer search or run: dir C:\Program Files\Autodesk\AutoCAD 2025\ASMDATAX230A.dllAffected if The file ASMDATAX230A.dll exists in the AutoCAD 2025 installation folder
-
Confirm STP file import capability is availableIn AutoCAD, type 'IMPORT' or 'FILEIMPORT' in the command line, or attempt to open an STP file via File > Open and filter for .stp or .step files. Alternatively, check if STEP import is listed in the ribbon under Insert > Import > STEP.Affected if STP/STEP file import options are visible or functional in the AutoCAD interface, indicating the vulnerable parsing component is loaded and accessible
-
Check for recent AutoCAD patchesIn AutoCAD, type 'UPDATES' in the command line or check Help > Check for Updates. Alternatively, examine the installed updates via Windows Settings > Updates > View update history.Affected if No updates have been installed since the initial 2025 release, or the installed version remains below 2025.1.1
A user is affected if they have AutoCAD 2025 (any variant) installed with a version between 2025.0.0 and 2025.1.0 and the ASMDATAX230A.dll is present, as the vulnerability triggers when parsing malicious STP 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 · scoped2025.1.1
Apply the vendor patch from Autodesk for affected AutoCAD versions. Until patched, avoid opening STP files from untrusted or unknown sources.
2025.1.1 for AutoCAD 2025 and associated vertical products (Advance Steel, Architecture, Civil 3D, Electrical, Mechanical, MEP, Plant 3D)
- 1. Back up all AutoCAD custom settings, scripts, and user profiles before upgrading
- 2. Close all running AutoCAD instances and related processes
- 3. Download AutoCAD 2025.1.1 (or your specific product's 2025.1.1 release) from Autodesk Account at manage.autodesk.com or the official Autodesk website
- 4. Run the downloaded installer with administrator privileges
- 5. Follow the on-screen installation wizard prompts to complete the upgrade
- 6. After installation completes, launch AutoCAD and verify the version by typing 'ABOUT' at the command prompt - confirm it shows version 2025.1.1
- 7. Test critical STP file workflows to ensure functionality is intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8597 — 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-8597 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