dbcve.org
Advance SteelApplication · Autodesk

CVE-2024-37005

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 force an Out-of-Bound Read. 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

A maliciously crafted X_B file parsed by pskernel.DLL in Autodesk applications triggers an out-of-bounds read vulnerability. An attacker can exploit this to cause application crashes, read sensitive memory contents, or potentially achieve arbitrary code execution within the current process context.

MitigationApply the official Autodesk security update/patch for pskernel.DLL when available. Until then, avoid opening X_B files from untrusted or unknown sources.

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
Advance SteelApplication
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
Autocad Plant 3dApplication
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 MechanicalApplication
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 ElectricalApplication
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

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 Autodesk product
    Open Windows Settings > Apps & Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' via PowerShell to list installed Autodesk applications
    Affected if Any of these products are installed: Advance Steel, Civil 3D, AutoCAD Plant 3D, AutoCAD MEP, AutoCAD Mechanical, AutoCAD Map 3D, AutoCAD Electrical, or AutoCAD Architecture
  2. Determine the installed product version
    Check the application version via Help > About in the Autodesk application, or locate the product's main executable (e.g., acadv2024.exe, steel2024.exe) in Program Files and view its version properties
    Affected if The version falls within any of these ranges: 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 version
    Search for pskernel.DLL in the product installation directory (typically under C:\Program Files\Autodesk\) and view the file version properties via right-click > Properties > Details
    Affected if The DLL version cannot be directly mapped to the affected version ranges; rely on the product version check instead
  4. Confirm X_B file handling capability
    Check if the product can import, open, or process X_B files (a steel/structure file format used in certain Autodesk products) by reviewing available file import options within the application
    Affected if The product supports X_B file import or processing, making the vulnerability reachable if the version is within the affected range

The environment is affected if an installed Autodesk product version (2022, 2023, 2024, or 2025) is lower than the first fixed release (2022.1.5, 2023.1.6, 2024.1.5, or 2025.1 respectively) and the product handles X_B 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 2022.1.5 / 2023.1.6 / 2024.1.5 or later
Fixed in 2022.1.52023.1.62024.1.5
Interim mitigation

Apply the official Autodesk security update/patch for pskernel.DLL when available. Until then, avoid opening X_B files from untrusted or unknown sources.

Recommended fix High confidence

Minimum fixed versions: 2022.1.5, 2023.1.6, 2024.1.5, or 2025.1 (depending on product line)

  1. Identify the specific Autodesk application (e.g., AutoCAD Civil 3D, AutoCAD Architecture, etc.) and version currently installed
  2. Navigate to the application's About screen or use the VER command in AutoCAD to confirm the exact version number
  3. If running version 2022, upgrade to version 2022.1.5 or later
  4. If running version 2023, upgrade to version 2023.1.6 or later
  5. If running version 2024, upgrade to version 2024.1.5 or later
  6. If running version 2025, upgrade to version 2025.1 or later
  7. Download the update from the Autodesk Account portal or through the application's update mechanism
  8. Install the update following Autodesk's standard installation procedures
Caveat Standard Autodesk upgrade considerations apply—ensure custom scripts, plugins, and dependent software are compatible with the new version before deploying broadly

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

Fix this in Advance Steel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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