dbcve.org
AutocadApplication · Autodesk

CVE-2024-23142

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 CATPART, STP, and MODEL file, when parsed in atf_dwg_consumer.dll, rose_x64_vc15.dll and libodxdll through Autodesk applications, can cause a use-after-free vulnerability. 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 · high confidence

A use-after-free vulnerability exists in Autodesk applications when parsing maliciously crafted CATPART, STP, and MODEL files through the atf_dwg_consumer.dll, rose_x64_vc15.dll, and libodxdll libraries. The vulnerability allows memory corruption that can be leveraged for arbitrary code execution within the context of the running process.

MitigationApply vendor-supplied patches from Autodesk for affected products and avoid opening untrusted CATPART, STP, or MODEL files 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.4>= 2025, < 2025.1
Autocad ArchitectureApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad ElectricalApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad Map 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad MechanicalApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad MepApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad Plant 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Civil 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 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
    Open Windows Settings > Apps > Apps & Features and look for any installed Autodesk application listed (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D). Alternatively, check Program Files for Autodesk folders.
    Affected if Any of these eight products is installed
  2. Check installed version number
    Open the Autodesk application, go to Help > About AutoCAD (or similar About dialog for your product), or check Windows Programs and Features to view the installed version. Note the full version number (for example: 2023.0.1 or 2024.1.0).
    Affected if Version number is visible and can be compared to the affected ranges
  3. Compare version to affected ranges
    Check if your installed version falls into any of these ranges: 2022.0 through 2022.1.4 (vulnerable), 2023.0 through 2023.1.5 (vulnerable), 2024.0 through 2024.1.3 (vulnerable), or 2025.0 (vulnerable). Versions 2022.1.5 and above, 2023.1.6 and above, 2024.1.4 and above, or 2025.1 and above are not affected.
    Affected if Installed version is within any of the vulnerable ranges listed
  4. Determine if file parsing feature is accessible
    The vulnerability triggers when parsing CATPART, STP, or MODEL files. Check if your workflow involves opening or importing these file types in the affected Autodesk product. The vulnerability exists regardless of file source, but exploitation requires opening a malicious file.
    Affected if You regularly open or import CATPART, STP, or MODEL files in the affected product version

Your environment is affected if you have any of the eight listed Autodesk products installed with a version number within 2022.0-2022.1.4, 2023.0-2023.1.5, 2024.0-2024.1.3, or 2025.0.

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.4 or later
Fixed in 2022.1.52023.1.62024.1.4
Interim mitigation

Apply vendor-supplied patches from Autodesk for affected products and avoid opening untrusted CATPART, STP, or MODEL files until patches are applied.

Recommended fix High confidence

2022.1.5 (or later for 2022), 2023.1.6 (or later for 2023), 2024.1.4 (or later for 2024), 2025.1 (or later for 2025)

  1. Identify the exact version of the installed Autodesk product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D) by opening the application and navigating to Help > About Autodesk <product>.
  2. Close all Autodesk applications completely.
  3. Download the appropriate update package from the Autodesk official support website (www.autodesk.com/support) for your specific product version.
  4. For AutoCAD 2022: Update to version 2022.1.5 or later.
  5. For AutoCAD 2023: Update to version 2023.1.6 or later.
  6. For AutoCAD 2024: Update to version 2024.1.4 or later.
  7. For AutoCAD 2025: Update to version 2025.1 or later.
  8. Run the downloaded installer and follow the on-screen prompts to install the update.
Caveat Point releases typically include backward-compatible fixes; test critical workflows after updating

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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