AutocadApplication · Autodesk

CVE-2024-23132

HIGH · 7.8 CVSS v3.1 Published 2024-02-22
Fix available
A fix is available. Upgrade to 2021.1.4 / 2022.1.4 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 STP file in atf_dwg_consumer.dll when parsed through Autodesk applications can lead to a memory corruption vulnerability by write access violation. This vulnerability in conjunction with other vulnerabilities could lead to code execution 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 · moderate confidence

A memory corruption vulnerability exists in atf_dwg_consumer.dll where parsing a maliciously crafted STP file triggers a write access violation. This can be chained with other vulnerabilities to achieve code execution in the current process context.

MitigationApply the vendor patch or update Autodesk applications to the latest version to remediate this vulnerability.

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:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad ArchitectureApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad ElectricalApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad MechanicalApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad MepApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad Plant 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Civil 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Advance SteelApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.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 Autodesk products
    Open Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed software
    Affected if Any of the following products appear: Autodesk AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel
  2. Verify product version
    Right-click the installed application exe, select Properties, then check the Details tab for File Version or Product Version. Alternatively, run the application and check Help > About
    Affected if The version is 2021.x, 2022.x, 2023.x, 2024.x, or 2025.x and falls below the patched release (2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, or 2025.0.1)
  3. Locate the vulnerable DLL
    Search the Autodesk installation directory for atf_dwg_consumer.dll. Default paths are typically C:\Program Files\Autodesk\ or C:\Program Files (x86)\Autodesk\
    Affected if The DLL atf_dwg_consumer.dll exists in the product installation folder, indicating the vulnerable component is present

You are affected if you have any of the listed Autodesk products installed with a version in the 2021 through 2025 range that is older than the patched releases (2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, or 2025.0.1) and the atf_dwg_consumer.dll file is present.

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 2021.1.4 / 2022.1.4 / 2023.1.5 or later
Fixed in 2021.1.42022.1.42023.1.5
Interim mitigation

Apply the vendor patch or update Autodesk applications to the latest version to remediate this vulnerability.

Recommended fix Moderate confidence

Upgrade to the following minimum versions based on your product: AutoCAD/AutoCAD Architecture/Electrical/Mechanical/MEP/Plant 3D 2021.1.4+, 2022.1.4+, 2023.1.5+, or 2024.1.3+ | Civil 3D 2021.1.4+, 2022.1.4+, 2023.1.5+, or 2024.1.3+ | Advance Steel 2021.1.4+, 2022.1.4+, 2023.1.5+, or 2024.1.3+

  1. 1. Identify the exact version of the installed Autodesk product by opening the application, going to Help > About Autodesk [Product Name], and noting the full version number.
  2. 2. Navigate to the Autodesk Account portal at https://account.autodesk.com/ or the official Autodesk support site to access updates and patches.
  3. 3. Locate the appropriate security update for CVE-2024-23132 in the Autodesk Product Support or Security Advisories section.
  4. 4. Download the update corresponding to your product line: For AutoCAD 2021.x, download version 2021.1.4 or later; for 2022.x, download 2022.1.4 or later; for 2023.x, download 2023.1.5 or later; for 2024.x, download 2024.1.3 or later.
  5. 5. Close all running Autodesk applications and ensure any associated processes are terminated.
  6. 6. Run the downloaded installer with administrative privileges and follow the on-screen prompts to apply the security update.
  7. 7. After installation, restart the Autodesk application and verify the updated version by checking Help > About to confirm the patch was applied successfully.
  8. 8. As a supplementary mitigation, implement organizational controls to restrict the handling of untrusted STP files until the update is applied, and configure application sandboxing or endpoint protection where available.
Caveat Minor: Standard AutoCAD update with no major API or workflow changes expected; however, verify compatibility with any custom scripts or third-party add-ins after upgrading

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

Fix this in Autocad Scoped from the published advisory
  • Consultation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23132 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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