dbcve.org
AutocadApplication · Autodesk

CVE-2024-9996

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, 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

An out-of-bounds write vulnerability exists in acdb25.dll when parsing DWG files in Autodesk AutoCAD. A maliciously crafted DWG file can trigger memory corruption during parsing, potentially allowing an attacker to execute arbitrary code in the context of the current process.

MitigationApply the vendor security patch for AutoCAD when available. Avoid opening DWG files from untrusted or unknown sources until the patch is applied.

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 check Programs and Features in Control Panel to see which AutoCAD variant is installed (e.g., AutoCAD, AutoCAD Architecture, Civil 3D, etc.)
    Affected if Any of the affected products is installed: 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, type VER or INFO at the command line, or right-click the application shortcut and select Properties to view the version field. Compare the version number to the affected range.
    Affected if Version is 2025 or later but earlier than 2025.1.1 (e.g., 2025.0, 2025.0.1, 2025.1.0)
  3. Verify acdb25.dll is present
    Search for acdb25.dll in the AutoCAD installation directory (commonly C:\Program Files\Autodesk\AutoCAD 2025\). The presence of this DLL indicates the vulnerable component exists.
    Affected if acdb25.dll exists in the AutoCAD program folder
  4. Confirm DWG file handling is enabled
    AutoCAD inherently supports DWG file opening by default. Verify by attempting to open any DWG file or checking File > Open dialog shows DWG as a supported format.
    Affected if AutoCAD can open DWG files (default state for all affected products)

You are affected if you have any of the listed AutoCAD 2025 products installed with a version >= 2025 and < 2025.1.1, as the vulnerability triggers when opening a malicious DWG file.

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 the vendor security patch for AutoCAD when available. Avoid opening DWG files from untrusted or unknown sources until the patch is applied.

Recommended fix High confidence

2025.1.1

  1. Back up any custom files, templates, and drawings before updating
  2. Download the AutoCAD 2025.1.1 update from the official Autodesk website (www.autodesk.com) or through the Autodesk Desktop App
  3. Close all AutoCAD applications and any related processes
  4. Run the installer and follow the on-screen prompts to install the 2025.1.1 update
  5. After installation, restart AutoCAD and verify that the application launches successfully
  6. Test that DWG files can be opened and saved correctly to confirm the update was applied successfully
Caveat Review the AutoCAD 2025.1.1 release notes for any changes to commands, APIs, or workflow features that may affect existing projects

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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