dbcve.org
AutocadApplication · Autodesk

CVE-2024-9997

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 DWG file when parsed in acdb25.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 · high confidence

Memory corruption vulnerability in acdb25.dll (AutoCAD's DWG file parser) triggered by parsing a maliciously crafted DWG file. The vulnerability allows an attacker to crash the application, write sensitive data to memory, or achieve arbitrary code execution within the context of the running AutoCAD process.

MitigationApply vendor patches from Autodesk immediately when available. Until then, implement compensating controls: validate all DWG files before opening, restrict DWG file sources, disable automatic file parsing where possible, and deploy endpoint detection/response solutions.

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 LtApplication
Affected:>= 2025, < 2025.1.1
Autocad MechanicalApplication
Affected:>= 2025, < 2025.1.1
Autocad MepApplication
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
    Open AutoCAD and go to Help > About AutoCAD, or run the command 'ABOUT' in the command line. Note the exact product name displayed.
    Affected if The product is any of: AutoCAD, AutoCAD Advance Steel, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD LT, AutoCAD Mechanical, or AutoCAD MEP.
  2. Check installed AutoCAD version
    In AutoCAD, run the command 'VER' or 'ABOUT' to display the full version number, or check the installed program in Windows Control Panel > Programs and Features.
    Affected if The version number is 2025.x.x where x is any build number, or specifically 2025.0.x through 2025.0.9.
  3. Verify acdb25.dll version
    Locate acdb25.dll in the AutoCAD installation directory (typically C:\Program Files\Autodesk\AutoCAD 2025\), right-click the file, select Properties, and check the File Version tab.
    Affected if The DLL file exists and the version matches the AutoCAD 2025 base version without the 2025.1.1 patch applied.
  4. Confirm version is within affected range
    Compare your installed version (from step 2) against the vulnerable range: versions >= 2025.0.0 and < 2025.1.1. Versions 2025.1.1 and later are patched.
    Affected if Your version starts with 2025 but is lower than 2025.1.1 (for example, 2025.0, 2025.0.1, 2025.0.2, etc.).

If you have any AutoCAD 2025 product variant installed with a version lower than 2025.1.1, your environment is vulnerable when opening DWG 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

Apply vendor patches from Autodesk immediately when available. Until then, implement compensating controls: validate all DWG files before opening, restrict DWG file sources, disable automatic file parsing where possible, and deploy endpoint detection/response solutions.

Recommended fix High confidence

AutoCAD 2025.1.1 (and corresponding versions for Advance Steel, Architecture, Civil 3D, Electrical, LT, Mechanical, and MEP)

  1. Verify current AutoCAD product version by opening the application, clicking the 'About Autodesk' button (or typing 'ABOUT' at the command prompt), and noting the version number displayed
  2. Confirm the installed product is one of the affected: AutoCAD 2025, AutoCAD Advance Steel 2025, AutoCAD Architecture 2025, AutoCAD Civil 3D 2025, AutoCAD Electrical 2025, AutoCAD LT 2025, AutoCAD Mechanical 2025, or AutoCAD MEP 2025
  3. Close all running Autodesk applications completely
  4. Download AutoCAD 2025.1.1 (or later) from the Autodesk Account portal at manage.autodesk.com or through the Autodesk Desktop App
  5. Run the installer with administrative privileges and follow the on-screen prompts to install the update
  6. Restart the computer after installation completes
  7. Launch the updated AutoCAD product and verify the version shows 2025.1.1 or later to confirm the patch was applied
Caveat Review Autodesk release notes for 2025.1.1 for any feature changes, system requirements, or known issues before upgrading; ensure custom scripts/LISP routines are tested for compatibility

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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