dbcve.org
AutocadApplication · Autodesk

CVE-2024-37007

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 and X_T file, when parsed in pskernel.DLL through Autodesk applications, can cause a use-after-free vulnerability. 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 use-after-free vulnerability exists in pskernel.DLL when parsing maliciously crafted X_B and X_T files in Autodesk applications. The vulnerability occurs when memory is freed but still accessed during file parsing, which can be exploited to achieve code execution in the current process.

MitigationUsers should avoid opening untrusted or unverified X_B and X_T files in affected Autodesk applications until an official patch is available from Autodesk.

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 Autodesk product
    Open the application, go to Help > About Autodesk, or run the application and check the title bar or help menu for the exact product name (e.g., AutoCAD 2024, Civil 3D 2024, AutoCAD Architecture 2023)
    Affected if Product is AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D
  2. Determine installed version and build number
    In the application, use the VERSION or VER command at the command line, or check Help > About Autodesk for the full version string (e.g., 2024.1.2)
    Affected if Version is 2022.x before 2022.1.5, 2023.x before 2023.1.6, 2024.x before 2024.1.5, or 2025.x before 2025.1
  3. Locate pskernel.DLL file
    Search for pskernel.dll in the application install directory (typically C:\Program Files\Autodesk\[ProductName]\[Version]\) or use PowerShell: Get-ChildItem -Path 'C:\Program Files\Autodesk' -Filter pskernel.dll -Recurse
    Affected if pskernel.dll exists in the Autodesk application directory, confirming the vulnerable component is present
  4. Check for recent X_B or X_T file processing
    Review application logs, temp folders (e.g., %TEMP%\Autodesk) for recently opened .x_t or .x_b files, or use file explorer search for these extensions in recent documents
    Affected if User has recently opened or parsed X_B or X_T files in the affected application version

You are affected if you use AutoCAD or a variant (Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D) or Civil 3D version 2022 through 2025.1 and the installed version falls below the patched thresholds (2022.1.5, 2023.1.6, 2024.1.5, or 2025.1), especially if you open X_B or X_T files from untrusted sources.

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

Users should avoid opening untrusted or unverified X_B and X_T files in affected Autodesk applications until an official patch is available from Autodesk.

Recommended fix High confidence

Upgrade to the fixed point release: 2022.1.5 (for 2022 products), 2023.1.6 (for 2023 products), 2024.1.5 (for 2024 products), or 2025.1 (for 2025 products)

  1. Identify the specific Autodesk product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D) and version currently installed
  2. Navigate to the Autodesk Account portal or use the product's built-in update checker to check for available updates
  3. For AutoCAD 2022: Upgrade to version 2022.1.5 or later
  4. For AutoCAD 2023: Upgrade to version 2023.1.6 or later
  5. For AutoCAD 2024: Upgrade to version 2024.1.5 or later
  6. For AutoCAD 2025: Upgrade to version 2025.1 or later
  7. Apply the same version upgrade to the corresponding vertical product (Architecture, Electrical, Mechanical, MEP, Plant 3D, Map 3D, or Civil 3D)
  8. Restart the application after installing the update

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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