CVE-2024-8592
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 AcTranslators.exe 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 AcTranslators.exe when parsing maliciously crafted CATPART files in Autodesk AutoCAD. The vulnerability allows a malicious actor to cause a crash, write sensitive data, or execute arbitrary code 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, < 2024.1.6>= 2024, < 2024.1.6>= 2024, < 2024.1.6>= 2024, < 2024.1.6>= 2024, < 2024.1.6>= 2024, < 2024.1.6>= 2024, < 2024.1.6>= 2024, < 2024.1.6CVSS 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 productCheck the Windows Programs and Features list or registry under HKLM\SOFTWARE\Autodesk\AutoCAD for installed versions. Look for entries like 'AutoCAD 2024', 'AutoCAD Architecture 2024', 'AutoCAD Civil 3D 2024', etc.Affected if Any of the listed AutoCAD 2024 products are installed
-
Determine the exact installed versionRun the AutoCAD product and check Help > About, or query the registry key for the specific version number (e.g., 2024.0.x or 2024.1.x). Compare the full version string against the vulnerable range.Affected if The installed version is 2024.0.x through 2024.1.5 (i.e., >= 2024 but < 2024.1.6)
-
Locate AcTranslators.exeSearch for AcTranslators.exe in the product installation directory, typically under C:\Program Files\Autodesk\AutoCAD 2024\ or the variant-specific folder. Verify the file exists.Affected if AcTranslators.exe is present in the AutoCAD 2024 installation directory
-
Verify CATPART file handling is availableCheck if the CATIA translator or CATPART import functionality is loaded. In AutoCAD, verify whether the CATIA translator plugin (AtfCATIA) is available under the Import options or check if CATPART files can be opened.Affected if CATPART file import capability is present and enabled in the AutoCAD installation
A system is affected if it runs any AutoCAD 2024 variant (Architecture, Civil 3D, Electrical, Mechanical, MEP, Plant 3D, or base AutoCAD) with a version lower than 2024.1.6 and has the CATPART translation functionality available.
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 · scoped2024.1.6
Apply vendor-supplied patches or updates from Autodesk for affected AutoCAD installations. Until patched, avoid opening untrusted CATPART files from unknown sources.
Autocad 2024.1.6 or later (and corresponding 2024.1.6 releases for AutoCAD Advance Steel, Architecture, Civil 3D, Electrical, Mechanical, MEP, and Plant 3D)
- Back up all critical AutoCAD files and projects before applying any updates
- Download AutoCAD 2024.1.6 (or later) update from the official Autodesk website (www.autodesk.com)
- Run the installer with administrator privileges
- Follow the on-screen installation prompts to complete the update
- Verify the installed version by checking Help > About AutoCAD > Product Information
- Ensure AcTranslators.exe is updated as part of the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8592 — 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-8592 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