dbcve.org
AutocadApplication · Autodesk

CVE-2024-37002

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 MODEL file, when parsed in ASMkern229A.dllthrough Autodesk applications, can be used to uninitialized variables. This vulnerability, along with other vulnerabilities, could 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 malformed MODEL file processed by ASMkern229A.dll in Autodesk applications triggers use of uninitialized variables, which when combined with other vulnerabilities can lead to arbitrary code execution in the current process context.

MitigationApply the vendor patch from Autodesk when available; avoid opening untrusted or unknown MODEL files in affected Autodesk applications until the patch is 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 the application and check Help > About Autodesk [Product Name], or check Add/Remove Programs for the installed Autodesk application name
    Affected if any of the listed products (AutoCAD, AutoCAD Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, or Civil 3D) are installed
  2. Determine installed version number
    In the application, type VER or INFOCENTER at the command line, or view the version in Help > About. The version will appear as Year.Release.Update (e.g., 2024.1.3)
    Affected if the version falls within >= 2022 and < 2022.1.5, or >= 2023 and < 2023.1.6, or >= 2024 and < 2024.1.4, or >= 2025 and < 2025.1
  3. Locate the vulnerable DLL
    Navigate to the application installation directory (typically C:\Program Files\Autodesk\[Product]\[Version]) and search for ASMkern229A.dll
    Affected if ASMkern229A.dll exists in the application directory, indicating the component that contains the vulnerability is present
  4. Confirm MODEL file handling capability
    Verify the application can open or import MODEL files by checking File > Open file type dropdown, or attempt to open a test MODEL file
    Affected if the application supports MODEL file processing, which is the attack vector required for exploitation

If the installed Autodesk product version is within the affected ranges (2022 to <2022.1.5, 2023 to <2023.1.6, 2024 to <2024.1.4, or 2025 to <2025.1) and ASMkern229A.dll is present, the environment is potentially affected.

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 the vendor patch from Autodesk when available; avoid opening untrusted or unknown MODEL files in affected Autodesk applications until the patch is applied.

Recommended fix High confidence

Upgrade to the following minimum versions per product: AutoCAD 2022.1.5+, 2023.1.6+, 2024.1.4+, or 2025.1+ (and corresponding versions for AutoCAD Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, and Civil 3D)

  1. Identify the specific Autodesk product (e.g., AutoCAD, AutoCAD Architecture, Civil 3D, etc.) and current version installed
  2. Navigate to Autodesk Account or the specific product's support/download page on www.autodesk.com
  3. Locate and download the appropriate update: For 2022.x versions, download version 2022.1.5 or later; For 2023.x versions, download version 2023.1.6 or later; For 2024.x versions, download version 2024.1.4 or later; For 2025.x versions, download version 2025.1 or later
  4. Close all Autodesk applications before installing the update
  5. Run the installer and follow the on-screen prompts to apply the update
  6. Restart the system after installation completes
  7. Verify the installed version matches or exceeds the fixed version for your product line
Caveat Point releases typically have minimal breaking changes; however, ensure compatibility with any custom scripts, plugins, or workflows before deploying broadly in production environments

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,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 $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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