dbcve.org
AutocadApplication · Autodesk

CVE-2024-23146

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 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 · moderate confidence

A maliciously crafted X_B or X_T file parsed through pskernel.DLL in Autodesk AutoCAD triggers an out-of-bounds write vulnerability. This memory corruption issue can lead to crash, data corruption, or arbitrary code execution within the current process context.

MitigationApply vendor patches from Autodesk when available; until then, implement file validation controls and restrict processing of untrusted X_B/X_T files in AutoCAD environments.

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 AutoCAD product and version
    Check the Windows registry at HKLM\SOFTWARE\Autodesk\AutoCAD for the installed version, or look in Programs and Features for the exact product name and version number
    Affected if The installed version falls within the affected ranges: 2022 versions before 2022.1.5, 2023 versions before 2023.1.6, 2024 versions before 2024.1.4, or 2025 versions before 2025.1
  2. Confirm the specific AutoCAD variant
    Check Programs and Features or the registry key for the product code (e.g., ACAD for vanilla, ACADArchitecture, ACADElectrical, Civil3D, etc.) to identify which vertical product is installed
    Affected if The variant is any of: AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D, and the version matches the affected ranges in step 1
  3. Locate pskernel.DLL in the installation
    Search for pskernel.DLL within the AutoCAD installation directory, typically found in the base install folder or subdirectories like bin or ptalauncher
    Affected if The file pskernel.DLL exists in the AutoCAD installation directory, confirming the vulnerable component is present
  4. Verify file handling capability for X_B/X_T formats
    Check if the application is configured to handle .X_B and .X_T file extensions, or attempt to open a test X_B/X_T file in the application to confirm parsing occurs through pskernel.DLL
    Affected if The system can open and parse X_B or X_T files, meaning the attack surface is exposed if untrusted files are processed

You are affected if you have any AutoCAD 2022, 2023, 2024, or 2025 product installed with a version below the patched thresholds (2022.1.5, 2023.1.6, 2024.1.4, or 2025.1) and the application can process X_B/X_T files through pskernel.DLL.

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; until then, implement file validation controls and restrict processing of untrusted X_B/X_T files in AutoCAD environments.

Recommended fix High confidence

2022.1.5 (or later) | 2023.1.6 (or later) | 2024.1.4 (or later) | 2025.1 (or later)

  1. 1. Identify the currently installed AutoCAD version (2022, 2023, 2024, or 2025) and its specific sub-version number
  2. 2. For AutoCAD 2022: Upgrade to version 2022.1.5 or later
  3. 3. For AutoCAD 2023: Upgrade to version 2023.1.6 or later
  4. 4. For AutoCAD 2024: Upgrade to version 2024.1.4 or later
  5. 5. For AutoCAD 2025: Upgrade to version 2025.1 or later
  6. 6. Download the appropriate update from the Autodesk Account portal or use the Autodesk Access app to check for and install updates
  7. 7. After updating, verify that pskernel.DLL has been patched by checking the file properties
  8. 8. Avoid opening untrusted X_B or X_T files until the update is applied
Caveat Standard Autodesk update considerations apply - ensure compatibility with custom scripts, plugins, and workflows before deploying organization-wide

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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