dbcve.org
AutocadApplication · Autodesk

CVE-2024-23149

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 SLDDRW file, when parsed in ODXSW_DLL.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

An out-of-bounds read vulnerability exists in ODXSW_DLL.dll when parsing maliciously crafted SLDDRW files in Autodesk applications. The vulnerability allows a malicious actor to read sensitive data from memory boundaries, potentially leading to crash, information disclosure, or arbitrary code execution in the current process context.

MitigationApply the vendor patch from Autodesk when available, and implement defense-in-depth controls such as disabling or restricting SLDDRW file handling in untrusted contexts until the update is applied.

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 the installed Autodesk product
    Check Programs and Features or the application itself to determine which Autodesk application is installed (e.g., AutoCAD, AutoCAD Architecture, Civil 3D, etc.)
    Affected if The installed product matches one of the affected products listed in the CVE (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D)
  2. Check the installed version number
    Open the Autodesk application, go to Help > About, or check the version in Programs and Features. Compare the version to the affected ranges: 2022 versions before 2022.1.5; 2023 versions before 2023.1.6; 2024 versions before 2024.1.4; 2025 versions before 2025.1
    Affected if The installed version falls within any of the affected version ranges (2022 < 2022.1.5, 2023 < 2023.1.6, 2024 < 2024.1.4, or 2025 < 2025.1)
  3. Locate ODXSW_DLL.dll on the system
    Search the Autodesk installation directory (commonly found in C:\Program Files\Autodesk\) for ODXSW_DLL.dll. The file is typically located in the application bin folder
    Affected if ODXSW_DLL.dll exists in the Autodesk installation directory, indicating the vulnerable component is present
  4. Verify SLDDRW file handling is enabled
    Check if the application has file associations or plugins configured to handle .SLDDRW files. This can be verified by attempting to open a SLDDRW file or checking the application's supported file types
    Affected if The application can open or process SLDDRW files, meaning the vulnerable parsing code path could be triggered

A system is affected if it has any of the listed Autodesk products installed with a version matching the affected ranges AND the ODXSW_DLL.dll component is present AND SLDDRW file handling is available.

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 the vendor patch from Autodesk when available, and implement defense-in-depth controls such as disabling or restricting SLDDRW file handling in untrusted contexts until the update is applied.

Recommended fix High confidence

AutoCAD 2022.1.5, 2023.1.6, 2024.1.4, or 2025.1 (and corresponding vertical product versions)

  1. Identify the exact version of the installed Autodesk product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D).
  2. Navigate to the Autodesk Account portal or official Autodesk support website to obtain the security update.
  3. Download the appropriate fixed version: For 2022 products, download version 2022.1.5 or later; For 2023 products, download version 2023.1.6 or later; For 2024 products, download version 2024.1.4 or later; For 2025 products, download version 2025.1 or later.
  4. Install the update using the Autodesk Desktop App or by running the downloaded installer with administrator privileges.
  5. Restart the application after installation completes.
  6. Verify the installed version matches or exceeds the fixed version to confirm the patch was applied successfully.
Caveat Standard Autodesk point release update; review release notes for any changes to features or workflow

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