dbcve.org
AutocadApplication · Autodesk

CVE-2024-8599

HIGH · 7.8 CVSS v3.1 Published 2024-10-29
Fix available
A fix is available. Upgrade to 2025.1.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A maliciously crafted STP 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 · moderate confidence

A memory corruption vulnerability exists in ACTranslators.exe when parsing maliciously crafted STP (STEP) files in Autodesk AutoCAD. The vulnerability allows an attacker to cause a crash, write sensitive data, or execute arbitrary code within the current process context.

MitigationUsers should avoid opening untrusted STP files from unknown or unverified sources and apply vendor patches from Autodesk when available.

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
AutocadApplication
Affected:>= 2025, < 2025.1.1
Autocad Advance SteelApplication
Affected:>= 2025, < 2025.1.1
Autocad ArchitectureApplication
Affected:>= 2025, < 2025.1.1
Autocad Civil 3dApplication
Affected:>= 2025, < 2025.1.1
Autocad ElectricalApplication
Affected:>= 2025, < 2025.1.1
Autocad MechanicalApplication
Affected:>= 2025, < 2025.1.1
Autocad MepApplication
Affected:>= 2025, < 2025.1.1
Autocad Plant 3dApplication
Affected:>= 2025, < 2025.1.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed AutoCAD product variant
    Open AutoCAD and go to Help > About, or check Add/Remove Programs for the installed Autodesk product name (e.g., AutoCAD 2025, AutoCAD Civil 3D 2025, AutoCAD Architecture 2025, etc.)
    Affected if The installed product is AutoCAD, AutoCAD Advance Steel, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, or AutoCAD Plant 3D
  2. Locate ACTranslators.exe in the installation directory
    Navigate to the AutoCAD installation folder (typically C:\Program Files\Autodesk\AutoCAD 2025\) and verify that ACTranslators.exe exists
    Affected if ACTranslators.exe is present in the AutoCAD installation directory
  3. Check the installed version number
    In AutoCAD, type VER or INFO at the command line, or right-click the ACTranslators.exe file in Explorer and view Properties > Details to see the File Version
    Affected if The version is 2025.0.0.0 through 2025.1.0.x (i.e., >= 2025 but < 2025.1.1)

You are affected if you have any of the listed AutoCAD 2025 variants installed with a version lower than 2025.1.1 and the ACTranslators.exe component is present on your system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2025.1.1 or later
Fixed in 2025.1.1
Interim mitigation

Users should avoid opening untrusted STP files from unknown or unverified sources and apply vendor patches from Autodesk when available.

Recommended fix High confidence

2025.1.1 or later

  1. 1. Close all AutoCAD applications and any related processes
  2. 2. Verify your current AutoCAD version by clicking Help > About AutoCAD
  3. 3. Open Autodesk Account or use the Autodesk Desktop App to check for available updates
  4. 4. Download and install AutoCAD 2025.1.1 or later from the official Autodesk website
  5. 5. Restart your system after installation completes
  6. 6. Verify the installed version matches or exceeds 2025.1.1 by checking Help > About AutoCAD
Caveat Review release notes for any workflow changes; test custom scripts and third-party plugins with the new version before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8599 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8599 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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