dbcve.org
AutocadApplication · Autodesk

CVE-2024-8590

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 3DM file when parsed in atf_api.dll through Autodesk AutoCAD can force a Use-After-Free 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 use-after-free vulnerability exists in Autodesk AutoCAD's atf_api.dll when parsing maliciously crafted 3DM files. The vulnerability occurs during file parsing where memory is freed but still accessed, potentially allowing an attacker to crash the application, disclose sensitive data, or execute arbitrary code in the context of the current process.

MitigationDo not open 3DM files from untrusted or unknown sources. Apply the vendor-provided security patch for Autodesk AutoCAD when released.

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 the installed AutoCAD product variant
    Open AutoCAD and go to Help > About Autodesk AutoCAD, or check Add/Remove Programs for the specific product name (AutoCAD, AutoCAD Architecture, AutoCAD Civil 3D, etc.)
    Affected if The product is one of: AutoCAD, AutoCAD Advance Steel, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, or AutoCAD Plant 3D
  2. Determine the installed version number
    In AutoCAD, type VER or HELP > About and read the version string. Alternatively, check the installation folder properties or the executable file properties for the version info.
    Affected if The version is 2025.0, 2025.0.0, or any 2025.x build prior to 2025.1.1
  3. Verify atf_api.dll exists in the installation
    Navigate to the AutoCAD installation directory (typically C:\Program Files\Autodesk\AutoCAD 2025\) and locate atf_api.dll
    Affected if The atf_api.dll file is present, as this is the library containing the vulnerable code
  4. Confirm the 3DM file import feature is accessible
    Try to open or import a 3DM file using the OPEN, IMPORT, or 3DMIMPORT command in AutoCAD
    Affected if The 3DM import functionality is available and can be triggered by opening a 3DM file

You are affected if you have any of the listed AutoCAD 2025 products with a version below 2025.1.1 and the atf_api.dll library is present, as the use-after-free vulnerability triggers when parsing 3DM 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

Do not open 3DM files from untrusted or unknown sources. Apply the vendor-provided security patch for Autodesk AutoCAD when released.

Recommended fix High confidence

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

  1. Verify your current AutoCAD version by clicking Help > About AutoCAD
  2. Close all AutoCAD applications and any related processes
  3. Back up any critical drawings and custom settings
  4. Download AutoCAD 2025.1.1 or your specific product's 2025.1.1 update from the Autodesk Account portal (accounts.autodesk.com) or the official Autodesk website
  5. Run the installer as an administrator
  6. Follow the on-screen installation prompts
  7. Restart your workstation after installation completes
  8. Launch the updated AutoCAD product and verify the version shows 2025.1.1

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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