dbcve.org
AutocadApplication · Autodesk

CVE-2024-37000

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 X_B file, when parsed in pskernel.DLL through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, in conjunction with other vulnerabilities, can lead to code execution 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 · moderate confidence

A maliciously crafted X_B file parsed by pskernel.DLL in Autodesk applications triggers a memory corruption vulnerability via write access violation, potentially enabling code execution when chained with other vulnerabilities.

MitigationAvoid opening untrusted X_B files in affected Autodesk applications until vendor patches are applied; implement input validation and bounds checking in the X_B file parsing logic within pskernel.DLL.

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 go to Help > About Autodesk, or check Add/Remove Programs for installed Autodesk software. Common product names include AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, and Civil 3D.
    Affected if The installed product matches one of the affected products listed in the CVE (AutoCAD or any variant, Civil 3D)
  2. Check installed version number
    In the application, type "VER" or "VERI" at the command line and press Enter, or go to Help > About Autodesk to view the exact version and build number.
    Affected if The version falls within any of these ranges: 2022 (before 2022.1.5), 2023 (before 2023.1.6), 2024 (before 2024.1.4), or 2025 (before 2025.1)
  3. Locate pskernel.DLL version
    Search for pskernel.DLL in the application installation directory (typically C:\Program Files\Autodesk\<ProductName>\). Right-click the file, select Properties, and check the Details tab for file version.
    Affected if The DLL version corresponds to an affected product version as determined in step 2
  4. Verify X_B file handling capability
    Check if the application has the ability to import or open X_B files. Look for X_B in the File > Open or File > Import dialogs, or search for file associations with .x_b extension in Windows registry under HKEY_CLASSES_ROOT\.x_b.
    Affected if X_B file handling is available and the version is within the affected ranges

You are affected if you have any of the listed Autodesk products installed with versions 2022 < 2022.1.5, 2023 < 2023.1.6, 2024 < 2024.1.4, or 2025 < 2025.1 and you use X_B file functionality.

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

Avoid opening untrusted X_B files in affected Autodesk applications until vendor patches are applied; implement input validation and bounds checking in the X_B file parsing logic within pskernel.DLL.

Recommended fix High confidence

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

  1. Identify the specific Autodesk product (e.g., AutoCAD, Civil 3D, AutoCAD Electrical) and version currently installed
  2. Determine which year-based release (2022, 2023, 2024, or 2025) corresponds to the installed version
  3. Obtain the appropriate update or subscription to access the latest version from Autodesk
  4. Download and install the fixed version: 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, or 2025.1 or later for 2025-based products
  5. Verify the installed version matches or exceeds the minimum fixed version for your product line
  6. Test that critical workflows function correctly after the update
Caveat Minor update within same release year; verify compatibility with any custom scripts or third-party add-ons before deploying

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,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 $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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