dbcve.org
AutocadApplication · Autodesk

CVE-2024-0446

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, CATPART or MODEL file, when parsed in ASMKERN228A.dll and ASMdatax229A.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

Out-of-bounds write vulnerability in AutoCAD's ASMKERN228A.dll and ASMdatax229A.dll parsing libraries when processing maliciously crafted STP, CATPART, or MODEL files. The parser writes beyond allocated buffer boundaries during file processing, allowing potential crash, memory corruption, or arbitrary code execution in the current process context.

MitigationApply vendor patch from Autodesk when available; avoid opening untrusted STEP, CATPART, or MODEL files in AutoCAD until patched.

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 the installed AutoCAD product and version
    Open AutoCAD, go to Help > About AutoCAD, or check the executable file properties (acad.exe) to view the version number and product name (e.g., AutoCAD 2023, AutoCAD Architecture 2024)
    Affected if The installed version falls within any of the affected ranges: 2021.x (< 2021.1.4), 2022.x (< 2022.1.4), 2023.x (< 2023.1.5), 2024.x (< 2024.1.3), or 2025.x (< 2025.0.1)
  2. Locate the vulnerable parsing DLLs
    Search for ASMKERN228A.dll and ASMdatax229A.dll in the AutoCAD installation directory (typically C:\Program Files\Autodesk\AutoCAD VERSION\)
    Affected if These DLLs exist in the AutoCAD installation folder, indicating the vulnerable parsing component is present
  3. Verify file association or ability to open STEP files
    Check if AutoCAD can open or import .STP (STEP) files by attempting to open a test file or checking File > Open file type filters
    Affected if AutoCAD is configured to open or import STEP, CATPART, or MODEL files, enabling the vulnerable parsing code path
  4. Confirm the product vertical (optional)
    Check if the installation is a specialized vertical product (AutoCAD Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, or Advance Steel) by examining the product name in Help > About or the installation folder name
    Affected if The installed product is any of the affected verticals (Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, or Advance Steel) within the same version ranges

The environment is affected if the installed AutoCAD product version (including verticals) is 2021.1.3 or lower, 2022.1.3 or lower, 2023.1.4 or lower, 2024.1.2 or lower, or 2025.0.0, and the application can process STP, CATPART, or MODEL files.

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 vendor patch from Autodesk when available; avoid opening untrusted STEP, CATPART, or MODEL files in AutoCAD until patched.

Recommended fix High confidence

Upgrade to AutoCAD and related products: 2021.1.4 or later; 2022.1.4 or later; 2023.1.5 or later; 2024.1.3 or later

  1. Identify the exact version of Autodesk product(s) installed by opening the application and navigating to Help > About AutoCAD (or equivalent menu for your product)
  2. Download the appropriate update from Autodesk's official support website for your specific product and version (2021, 2022, 2023, or 2024)
  3. Ensure all running instances of AutoCAD or related products are closed before applying the update
  4. Run the downloaded update installer with administrator privileges
  5. Follow the on-screen installation prompts and wait for completion
  6. Restart the application and verify the version shows the patched release (2021.1.4+, 2022.1.4+, 2023.1.5+, or 2024.1.3+)
  7. Test with sample files to confirm normal operation
Caveat Point releases typically include bug fixes and security patches with minimal risk; always review Autodesk release notes before deployment in production environments

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

Fix this in Autocad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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