CVE-2024-8593
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 CATPART file, when parsed in ASMKERN230A.dll through Autodesk AutoCAD, may force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, 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 confidenceAn out-of-bounds write vulnerability exists in ASMKERN230A.dll when Autodesk AutoCAD parses maliciously crafted CATPART files (CATIA format). The vulnerability allows a malicious actor to trigger memory corruption, potentially leading to crash, data corruption, or 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>= 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.
-
Identify installed AutoCAD product variantOpen AutoCAD and go to Help > About Autodesk AutoCAD, or run the VER command in the command line to see which product variant (AutoCAD, AutoCAD Architecture, Civil 3D, etc.) is installed.Affected if The installed product is any of: AutoCAD, AutoCAD Advance Steel, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, or AutoCAD Plant 3D.
-
Check installed AutoCAD version numberIn AutoCAD, type 'VER' or 'ABOUT' in the command line, or check Add/Remove Programs for the version. Look for the full version string (e.g., 2025.0, 2025.0.1).Affected if The version is 2025.0 through 2025.1.0 (any version >= 2025 but < 2025.1.1).
-
Locate and verify the ASMKERN230A.dll versionSearch for ASMKERN230A.dll in the AutoCAD installation directory (typically C:\Program Files\Autodesk\AutoCAD 2025\). Right-click the file, select Properties, and check the File Version tab.Affected if The DLL exists and has a version that corresponds to an unpatched AutoCAD 2025 release.
-
Confirm CATIA/CATPART file support is enabledIn AutoCAD, go to Options (type OPTIONS) > Files tab > Asset Library and File References, or check if the ETIMPORT or CATIA importers are loaded. The vulnerability triggers when parsing CATPART files, so this feature must be active.Affected if CATIA import support or the ASMKERN230A.dll module is loaded or available in the installation.
You are affected if you have any 2025-variant AutoCAD product installed with a version >= 2025 and < 2025.1.1, and the ASMKERN230A.dll module for CATIA/CATPART file parsing is present in your installation.
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 or update Autodesk AutoCAD to a version that addresses CVE-2024-8593. Until patched, avoid opening untrusted CATPART files from unknown sources.
AutoCAD 2025.1.1 (and corresponding 2025.1.1 updates for AutoCAD-based products)
- Back up all drawings, templates, and custom settings before upgrading
- Navigate to the Autodesk AutoCAD download page or use the Autodesk Desktop App to check for updates
- Download the AutoCAD 2025.1.1 update or the specific product update (e.g., AutoCAD Civil 3D 2025.1.1) from www.autodesk.com
- Run the installer and follow the on-screen prompts to install the update
- After installation, verify the version by typing 'ABOUT' in the command line and confirming the version shows 2025.1.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8593 — 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-8593 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