dbcve.org
AutocadApplication · Autodesk

CVE-2024-8600

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 SLDPRT file when parsed in odxsw_dll.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 · moderate confidence

A memory corruption vulnerability exists in Autodesk AutoCAD's odxsw_dll.dll component when parsing maliciously crafted SLDPRT (SolidWorks part) files. The vulnerability allows a malicious actor to cause a crash, write sensitive data, or execute arbitrary code in the context of the current process.

MitigationAvoid opening untrusted or unverified SLDPRT files in AutoCAD. Apply Autodesk security patches when released. Consider implementing file type restrictions or sandboxing for SLDPRT imports until a patch is 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 installed AutoCAD product and version
    Open AutoCAD, click Help > About Autodesk AutoCAD, or type 'VER' or 'ABOUT' at the command line. Note the exact version number (for example, 2025.0 or 2025.1). Alternatively, check Programs and Features in Control Panel for the installed version.
    Affected if The installed version is 2025.0 through 2025.1.0 (anything >= 2025 but < 2025.1.1)
  2. Confirm the specific AutoCAD variant
    Check Programs and Features or the Help > About dialog to identify which AutoCAD product is installed (AutoCAD, AutoCAD Architecture, Civil 3D, Electrical, Mechanical, MEP, Plant 3D, or Advance Steel).
    Affected if The product is any of the affected variants: AutoCAD, Advance Steel, Architecture, Civil 3D, Electrical, Mechanical, MEP, or Plant 3D, and the version is in the vulnerable range.
  3. Locate the odxsw_dll.dll component
    Search for odxsw_dll.dll in the AutoCAD installation directory (typically C:\Program Files\Autodesk\AutoCAD 2025\ or C:\Program Files\Autodesk\AutoCAD<variant> 2025\). Use Windows Explorer search or run: dir /s C:\Program Files\Autodesk\*odxsw_dll.dll
    Affected if The file odxsw_dll.dll exists in the AutoCAD 2025 installation folder, indicating the vulnerable component is present.
  4. Check if SLDPRT file import is used
    Review recent file history or ask users if they open SolidWorks part files (.SLDPRT) in AutoCAD. Check for recent .sldprt files in the system or document folders.
    Affected if Users routinely import or open SLDPRT files, as this is the attack vector required to trigger the vulnerability.

You are affected if you have any AutoCAD 2025 variant installed with a version between 2025.0 and 2025.1.0 inclusive and users open SLDPRT files in that environment.

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

Avoid opening untrusted or unverified SLDPRT files in AutoCAD. Apply Autodesk security patches when released. Consider implementing file type restrictions or sandboxing for SLDPRT imports until a patch is available.

Recommended fix High confidence

AutoCAD 2025.1.1 (and corresponding updates for AutoCAD-based products: Advance Steel 2025.1.1, AutoCAD Architecture 2025.1.1, Civil 3D 2025.1.1, AutoCAD Electrical 2025.1.1, AutoCAD Mechanical 2025.1.1, AutoCAD MEP 2025.1.1, AutoCAD Plant 3D 2025.1.1)

  1. Backup all custom settings, scripts, and workspaces in AutoCAD before updating
  2. Ensure all active drawings are saved and closed
  3. Download AutoCAD 2025.1.1 (or later) from the official Autodesk website or Autodesk Account portal
  4. Run the installer with administrator privileges
  5. Follow the on-screen installation prompts to complete the update
  6. Launch AutoCAD and verify the version by typing 'ABOUT' or 'VER' in the command line to confirm version 2025.1.1 is installed
  7. Test opening previously used SLDPRT files to ensure functionality is maintained
Caveat Point release upgrade with minimal risk; standard upgrade precautions apply (backup data, test critical workflows)

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8600 — 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-8600 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