dbcve.org
AutocadApplication · Autodesk

CVE-2024-8596

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 MODEL file, when parsed in libodxdll.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 confidence

A crafted MODEL file parsed by libodxdll.dll in Autodesk AutoCAD triggers an out-of-bounds write vulnerability, allowing an attacker to crash the application, corrupt data, or execute arbitrary code within the current process context.

MitigationAvoid opening untrusted or unverified MODEL files; apply vendor patches from Autodesk when available; implement file validation and sandboxing for file parsing operations.

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, go to Help > About AutoCAD, or run the VER command in the command line to retrieve the exact version number and product name
    Affected if The installed version is 2025.0 through 2025.1.0 (any build >= 2025 but < 2025.1.1)
  2. Locate libodxdll.dll
    Search for libodxdll.dll in the AutoCAD installation directory (typically C:\Program Files\Autodesk\AutoCAD 2025\) using File Explorer or PowerShell: Get-ChildItem -Path 'C:\Program Files\Autodesk' -Recurse -Filter 'libodxdll.dll'
    Affected if The DLL exists in the AutoCAD 2025 installation folder, confirming the vulnerable component is present
  3. Check if MODEL file handling is enabled or used
    Review recent activity logs, examine the AutoCAD recent documents list, or check the support file search path for .model file associations using the OPTIONS command
    Affected if The user opens, imports, or processes MODEL files within AutoCAD, as this is the required attack vector

You are affected if you are running any AutoCAD 2025 variant (including Advance Steel, Architecture, Civil 3D, Electrical, Mechanical, MEP, or Plant 3D) with a version lower than 2025.1.1 and you handle MODEL files.

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 MODEL files; apply vendor patches from Autodesk when available; implement file validation and sandboxing for file parsing operations.

Recommended fix High confidence

AutoCAD 2025.1.1 (and associated product variants: AutoCAD Advance Steel 2025.1.1, AutoCAD Architecture 2025.1.1, AutoCAD 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. Navigate to the official Autodesk website (www.autodesk.com) or your Autodesk Account portal
  2. Locate the download section for AutoCAD 2025 products
  3. Download AutoCAD 2025.1.1 (or the specific product variant such as AutoCAD Architecture 2025.1.1, AutoCAD Civil 3D 2025.1.1, etc.)
  4. Run the installer and follow the on-screen instructions to install the update
  5. Restart AutoCAD after installation completes
  6. Verify the installed version by typing 'VER' or 'ABOUT' in the AutoCAD command line to confirm version 2025.1.1 is running
Caveat Routine security update with no expected breaking changes; as with any software update, verify custom scripts and third-party integrations work correctly after upgrading

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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