dbcve.org
AutocadApplication · Autodesk

CVE-2024-23157

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 SLDASM or SLDPRT file, when parsed in ODXSW_DLL.dll through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, along with other vulnerabilities, can 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 memory corruption vulnerability in ODXSW_DLL.dll allows write access violation when parsing maliciously crafted SLDASM or SLDPRT files. This occurs due to improper bounds checking or input validation during file parsing, which can be exploited to achieve code execution in the current process.

MitigationApply the vendor patch for CVE-2024-23157 when available. Until then, avoid opening untrusted SLDASM or SLDPRT files in Autodesk applications, and consider running applications with reduced privileges to limit impact.

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 Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed Autodesk applications
    Affected if Any Autodesk product from the affected list (AutoCAD, AutoCAD Architecture, Electrical, Map 3d, Mechanical, MEP, Plant 3d, or Civil 3d) is present
  2. Determine the installed version
    In AutoCAD, type 'ABOUT' or 'VER' in the command line to display version information. Alternatively, right-click the desktop shortcut, select Properties, and check the target path for version details
    Affected if The version falls within any of these ranges: >=2022 and <2022.1.5, >=2023 and <2023.1.6, >=2024 and <2024.1.5, or >=2025 and <2025.1
  3. Locate ODXSW_DLL.dll
    Search for ODXSW_DLL.dll in the AutoCAD installation directory, typically found in C:\Program Files\Autodesk\[ProductName]\[Version]\. Use PowerShell: Get-ChildItem -Path 'C:\Program Files\Autodesk' -Recurse -Filter 'ODXSW_DLL.dll'
    Affected if The DLL exists in the product installation folder, indicating the vulnerable component is present
  4. Check DLL file version
    Right-click ODXSW_DLL.dll > Properties > Details tab to view File Version and Product Version. Or run: (Get-Item 'C:\Program Files\Autodesk\[Path]\ODXSW_DLL.dll').VersionInfo
    Affected if The file exists but the version is earlier than the patched version for your product line

You are affected if any of the listed Autodesk products (AutoCAD, Architecture, Electrical, Map 3d, Mechanical, MEP, Plant 3d, or Civil 3d) is installed with a version matching the affected ranges, and the ODXSW_DLL.dll component is present in the installation directory.

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 vendor patch for CVE-2024-23157 when available. Until then, avoid opening untrusted SLDASM or SLDPRT files in Autodesk applications, and consider running applications with reduced privileges to limit impact.

Recommended fix High confidence

Upgrade to version 2022.1.5 or later for 2022 products; 2023.1.6 or later for 2023 products; 2024.1.5 or later for 2024 products; 2025.1 or later for 2025 products

  1. Identify the currently installed Autodesk product and version from the application's About dialog or Add/Remove Programs
  2. Determine which version line (2022, 2023, 2024, or 2025) the installation belongs to
  3. Navigate to the Autodesk Support website (www.autodesk.com) or the direct download page for the specific product
  4. Download the update installer matching your product version: for 2022 products download 2022.1.5 or later, for 2023 products download 2023.1.6 or later, for 2024 products download 2024.1.5 or later, for 2025 products download 2025.1 or later
  5. Run the installer and follow the prompts to apply the security update
  6. Restart the Autodesk application after the update completes
  7. Verify the installed version reflects the patched release (e.g., 2022.1.5, 2023.1.6, 2024.1.5, or 2025.1)
Caveat Standard Autodesk update; review release notes for any workflow or compatibility changes before deploying in production environments

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

Fix this in Autocad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
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,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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