dbcve.org
AutocadApplication · Autodesk

CVE-2024-23159

HIGH · 7.8 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 2022.1.5 / 2023.1.6 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, when parsed in stp_aim_x64_vc15d.dll through Autodesk applications, can be used to uninitialized variables. This vulnerability, along with other vulnerabilities, can lead to code execution in 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 malformed STP (STEP CAD) file processed by stp_aim_x64_vc15d.dll in Autodesk applications triggers an uninitialized variable vulnerability that can be leveraged for code execution within the current process context.

MitigationApply vendor-supplied patches for affected Autodesk applications; do not open STP files from untrusted or unknown sources until patches are 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:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad ArchitectureApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad ElectricalApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad Map 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad MechanicalApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad MepApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad Plant 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Civil 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.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 product and version
    Open the application, go to Help > About Autodesk [Product], or check Programs and Features in Control Panel for the installed version
    Affected if The version falls within any of these ranges: AutoCAD/AutoCAD-based products 2022 (before 2022.1.5), 2023 (before 2023.1.6), 2024 (before 2024.1.5), or 2025 (before 2025.1)
  2. Confirm product type
    Determine if the installed product is one of: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D
    Affected if The product is any of these eight AutoCAD variants and the version is in the affected ranges listed above
  3. Check for the vulnerable DLL
    Search for stp_aim_x64_vc15d.dll in the application installation directory (commonly found in the bin folder under the product installation path)
    Affected if The DLL exists and its version cannot be determined or is earlier than the patched build corresponding to the version thresholds

You are affected if any of these Autodesk products (AutoCAD, AutoCAD Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, or Civil 3D) is installed with version 2022 before 2022.1.5, 2023 before 2023.1.6, 2024 before 2024.1.5, or 2025 before 2025.1.

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 2022.1.5 / 2023.1.6 / 2024.1.5 or later
Fixed in 2022.1.52023.1.62024.1.5
Interim mitigation

Apply vendor-supplied patches for affected Autodesk applications; do not open STP files from untrusted or unknown sources until patches are applied.

Recommended fix High confidence

Upgrade to version 2022.1.5, 2023.1.6, 2024.1.5, or 2025.1 depending on your product line

  1. Identify the specific Autodesk product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D) and current version installed
  2. Verify the current version falls within the affected range: 2022 through 2024 (prior to fixes) or 2025 (prior to 2025.1)
  3. Obtain the appropriate fixed version from Autodesk: 2022.1.5, 2023.1.6, 2024.1.5, or 2025.1
  4. Download the update from the official Autodesk website (www.autodesk.com) or through the Autodesk desktop application
  5. Close all Autodesk applications and any running processes related to the product
  6. Run the installer with administrator privileges and follow the on-screen prompts to complete the update
  7. Restart the system after installation to ensure all components are properly initialized
  8. Verify the installed version matches the fixed release to confirm the update was successful
Caveat Standard Autodesk version updates typically retain backward compatibility for DWG files; however, verify project compatibility and backup critical files before upgrading

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 / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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