dbcve.org
AutocadApplication · Autodesk

CVE-2024-8594

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 can force a Heap-Based Overflow 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 confidence

A heap-based buffer overflow vulnerability exists in libodxdll.dll when Autodesk AutoCAD parses a maliciously crafted MODEL file. The overflow allows an attacker to crash the application, write sensitive data to arbitrary memory locations, or execute arbitrary code within the current process context.

MitigationAvoid opening untrusted or unknown MODEL files in AutoCAD until Autodesk releases an official patch addressing the heap overflow in libodxdll.dll.

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 version
    Open AutoCAD and go to Help > About AutoCAD, or run the command 'ABOUT' in the command line to display the full version number including the build
    Affected if The displayed version is 2025.x but less than 2025.1.1 (for example, 2025.0, 2025.0.1, 2025.1.0)
  2. Locate libodxdll.dll in the installation directory
    Navigate to the AutoCAD installation folder (typically C:\Program Files\Autodesk\AutoCAD 2025\) and search for the file libodxdll.dll
    Affected if The file libodxdll.dll exists in the AutoCAD 2025 installation directory, confirming the presence of the vulnerable component
  3. Confirm product variant is affected
    Check which AutoCAD product variant is installed (Standard, Advance Steel, Architecture, Civil 3D, Electrical, Mechanical, MEP, or Plant 3D) by looking at the product name in Help > About or the installation folder name
    Affected if The installed product is one of the variants listed (Advance Steel, Architecture, Civil 3D, Electrical, Mechanical, MEP, or Plant 3D) running version 2025 through 2025.1.0

You are affected if you have any Autodesk AutoCAD 2025 variant installed with a version between 2025.0 and 2025.1.0 (inclusive) and the file libodxdll.dll is present in the installation directory.

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 unknown MODEL files in AutoCAD until Autodesk releases an official patch addressing the heap overflow in libodxdll.dll.

Recommended fix High confidence

2025.1.1 or later

  1. 1. Open AutoCAD 2025 and verify the current version by clicking Help > About AutoCAD
  2. 2. Navigate to your Autodesk account at account.autodesk.com or use the Autodesk Access app
  3. 3. Download AutoCAD 2025 version 2025.1.1 or later
  4. 4. Run the installer and follow the on-screen prompts to apply the update
  5. 5. After installation completes, restart AutoCAD
  6. 6. Verify the installed version is 2025.1.1 or higher by checking Help > About AutoCAD

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

Fix this in Autocad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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