dbcve.org
Autocad Map 3dApplication · Autodesk

CVE-2024-23143

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, MODEL and X_B file, when parsed in ASMkern229A.dll and ASMBASE229A.dll through Autodesk applications, can force an Out-of-Bound Read and/or Out-of-Bound Write. A malicious actor can leverage this vulnerability to cause a crash,read sensitive data, 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 memory read/write vulnerability in ASMkern229A.dll and ASMBASE229A.dll when parsing maliciously crafted 3DM, MODEL, and X_B files in Autodesk applications. This memory corruption can be exploited for denial of service, information disclosure, or arbitrary code execution in the current process context.

MitigationApply vendor patches from Autodesk when available; avoid opening untrusted 3DM, MODEL, or X_B files from unknown sources 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
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
Advance SteelApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
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

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 go to Help > About Autodesk [Product], or check Add/Remove Programs for the installed product name
    Affected if The product is one of: AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, Advance Steel, AutoCAD, or AutoCAD Architecture
  2. Determine installed version number
    In the application, type VER or ABOUT at the command line, or check the program version in Add/Remove Programs
    Affected if The version falls within any of these ranges: 2022 to <2022.1.5, 2023 to <2023.1.6, 2024 to <2024.1.4, or 2025 to <2025.1
  3. Locate vulnerable DLL files
    Search for ASMkern229A.dll and ASMBARE229A.dll in the application installation directory (commonly in C:\Program Files\Autodesk\[Product]\[Version])
    Affected if These DLLs exist in the application folder, indicating the vulnerable component is present
  4. Check if file parsing feature is used
    Inspect recent activity logs or user workflow to determine if the application has been used to open or import 3DM, MODEL, or X_B files
    Affected if Users have opened files with .3DM, .MODEL, or .X_B extensions in the affected application

You are affected if the installed product is any of the eight Autodesk applications listed and its version falls within 2022 to <2022.1.5, 2023 to <2023.1.6, 2024 to <2024.1.4, or 2025 to <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.4 or later
Fixed in 2022.1.52023.1.62024.1.4
Interim mitigation

Apply vendor patches from Autodesk when available; avoid opening untrusted 3DM, MODEL, or X_B files from unknown sources until patched.

Recommended fix High confidence

Upgrade to version 2022.1.5 or later for 2022 products; 2023.1.6 or later for 2023 products; 2024.1.4 or later for 2024 products; 2025.1 or later for 2025 products

  1. 1. Identify the specific Autodesk product and version currently installed (e.g., AutoCAD 2023, Civil 3D 2024, etc.)
  2. 2. Close all running Autodesk applications to prevent installation conflicts
  3. 3. Launch Autodesk Access or open the Autodesk Desktop App to check for available updates
  4. 4. Alternatively, navigate to the Autodesk Account portal at account.autodesk.com and sign in with your credentials
  5. 5. Locate the product in the 'All Products' section and click 'View Updates' or 'Download' for the available update
  6. 6. Download the update corresponding to your product line: 2022.1.5 or later for 2022-based products, 2023.1.6 or later for 2023-based products, 2024.1.4 or later for 2024-based products, 2025.1 or later for 2025-based products
  7. 7. Run the installer with administrator privileges and follow the on-screen prompts
  8. 8. Restart the system after installation completes
Caveat Standard Autodesk update; review release notes for any changes to features or workflows relevant to your deployment

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

Fix this in Autocad Map 3d Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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