dbcve.org
AutocadApplication · Autodesk

CVE-2024-23151

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 3DM file, when parsed in ASMkern229A.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 ASMkern229A.dll when parsing 3DM files in Autodesk AutoCAD. A maliciously crafted 3DM file can cause memory to be written beyond allocated buffer boundaries, potentially leading to crash, data corruption, or arbitrary code execution in the context of the current process.

MitigationApply the vendor-supplied security patch from Autodesk to update AutoCAD and the affected ASMkern229A.dll component. Until patched, avoid opening 3DM files from untrusted or unknown sources.

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 AutoCAD product and version
    Open AutoCAD, type 'ABOUT' in the command line to display version information, or check Add/Remove Programs for the installed version number
    Affected if The version falls within these ranges: 2022 (before 2022.1.5), 2023 (before 2023.1.6), 2024 (before 2024.1.5), or 2025 (before 2025.1)
  2. Verify the vulnerable DLL exists
    Locate ASMkern229A.dll in the AutoCAD installation directory (typically in the program files folder under the AutoCAD subfolder)
    Affected if The DLL is present and the version is unpatched - the vulnerability exists in this component when parsing 3DM files
  3. Confirm product type is affected
    Identify the specific AutoCAD variant installed (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D)
    Affected if The installed product is any of these eight variants with a version in the affected ranges

You are affected if you have any of the listed AutoCAD products (including Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, or Civil 3D) with version 2022 before 2022.1.5, 2023 before 2023.1.6, 2024 before 2024.1.5, or 2025 before 2025.1, and the ASMkern229A.dll file exists in your installation.

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 the vendor-supplied security patch from Autodesk to update AutoCAD and the affected ASMkern229A.dll component. Until patched, avoid opening 3DM files from untrusted or unknown sources.

Recommended fix High confidence

Upgrade to 2022.1.5 or later for 2022.x, 2023.1.6 or later for 2023.x, 2024.1.5 or later for 2024.x, or 2025.1 or later for 2025.x

  1. 1. Identify the specific AutoCAD-based product and version installed (e.g., AutoCAD 2023, Civil 3D 2024, etc.)
  2. 2. Close the Autodesk application completely
  3. 3. Navigate to the Autodesk Account or the Autodesk Product Support page at www.autodesk.com
  4. 4. Locate and download the appropriate update or service pack for your product version: for 2022.x download 2022.1.5 or later, for 2023.x download 2023.1.6 or later, for 2024.x download 2024.1.5 or later, for 2025.x download 2025.1 or later
  5. 5. Run the installer and follow the prompts to apply the update
  6. 6. Restart the application after installation completes
  7. 7. Verify the version by checking Help > About AutoCAD to confirm the installed version matches the patched release
Caveat Standard Autodesk update installation; review release notes for any workflow changes specific to your product

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

Fix this in Autocad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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