dbcve.org
Advance SteelApplication · Autodesk

CVE-2024-23138

HIGH · 7.8 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 2021.1.4 / 2022.1.4 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 DWG file when parsed through Autodesk DWG TrueView can be used to cause a Stack-based Overflow. 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 stack-based buffer overflow vulnerability in Autodesk DWG TrueView when parsing maliciously crafted DWG files, allowing attackers to potentially execute arbitrary code, read sensitive data, or cause a denial of service in the context of the current process.

MitigationApply the vendor security update from Autodesk for DWG TrueView, and implement controls to avoid opening untrusted DWG files from unknown or untrusted 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:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3
AutocadApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2022, < 2022.4.1>= 2023, < 2023.1.5>= 2023, < 2023.3.1>= 2024, < 2024.1.2>= 2024, < 2024.1.3
Autocad ArchitectureApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, <= 2023.1.5>= 2024, < 2024.1.3
Autocad ElectricalApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3
Autocad LtApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2022, < 2022.4.1>= 2023, < 2023.1.5>= 2023, < 2023.3.1>= 2024, < 2024.1.2>= 2024, < 2024.1.3
Autocad Map 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3
Autocad MechanicalApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3
Autocad MepApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.15>= 2024, < 2024.1.3

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 products
    Check the Windows registry under HKLM\SOFTWARE\Autodesk\AutoCAD or look in Program Files for Autodesk folders. Common paths: C:\Program Files\Autodesk\AutoCAD, C:\Program Files\Autodesk\Advance Steel
    Affected if Any Autodesk product from the affected list (Advance Steel, AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP) is present
  2. Determine the exact product version
    Open the installed application, go to Help > About AutoCAD (or equivalent), or run the application with the /version flag. Alternatively, check the registry key HKLM\SOFTWARE\Autodesk\AutoCAD\[Version]\InstallPath
    Affected if The installed version falls within any of the vulnerable ranges: 2021 before 2021.1.4, 2022 before 2022.1.4 or 2022.4.1, 2023 before 2023.1.5 or 2023.3.1, 2024 before 2024.1.2 or 2024.1.3
  3. Verify DWG parsing component is present
    Confirm the core DWG TrueView or AutoCAD engine files exist in the installation directory, typically in the bin folder (e.g., acad.exe, TrueView.exe)
    Affected if The DWG parsing executable (acad.exe, TrueView.exe, or similar) is present and functional, indicating the vulnerability can be triggered
  4. Check if the product processes untrusted DWG files
    Review system usage patterns or audit logs to determine if the application is used to open DWG files from external or untrusted sources
    Affected if Users open DWG files from unknown or untrusted sources, which would trigger the vulnerable parsing code

If an affected Autodesk product version is installed and processes DWG files, the environment is vulnerable to CVE-2024-23138.

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 2021.1.4 / 2022.1.4 / 2022.4.1 or later
Fixed in 2021.1.42022.1.42022.4.1
Interim mitigation

Apply the vendor security update from Autodesk for DWG TrueView, and implement controls to avoid opening untrusted DWG files from unknown or untrusted sources.

Recommended fix High confidence

Upgrade to the fixed version for your product line: 2021.1.4, 2022.1.4 (or 2022.4.1), 2023.1.5 (or 2023.15 for MEP), or 2024.1.3 depending on the year of your release

  1. Identify all installed Autodesk products affected by this vulnerability (Advance Steel, AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, or AutoCAD MEP)
  2. Check the current installed version of each affected product
  3. Navigate to the official Autodesk support website (www.autodesk.com) to download the appropriate security update
  4. For AutoCAD 2021.x users: upgrade to version 2021.1.4 or later
  5. For AutoCAD 2022.x users: upgrade to version 2022.1.4 (or 2022.4.1 for AutoCAD and AutoCAD LT) or later
  6. For AutoCAD 2023.x users: upgrade to version 2023.1.5 or later
  7. For AutoCAD 2024.x users: upgrade to version 2024.1.3 or later
  8. For AutoCAD MEP 2023.x users: upgrade to version 2023.15 or later
Caveat Minor version security patches typically do not introduce breaking changes; however, users should review Autodesk release notes for any behavior changes

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-23138 — 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-23138 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