dbcve.org
AutocadApplication · Autodesk

CVE-2024-23127

HIGH · 7.8 CVSS v3.1 Published 2024-02-22
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 MODEL, SLDPRT, or SLDASM file, when parsed in ODXSW_DLL.dll and libodxdll.dll through Autodesk applications, can be used to cause a Heap-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

Heap-based buffer overflow in ODXSW_DLL.dll and libodxdll.dll when Autodesk applications parse maliciously crafted MODEL, SLDPRT, or SLDASM files. The overflow allows arbitrary code execution in the context of the current process.

MitigationAvoid opening untrusted MODEL, SLDPRT, or SLDASM files until Autodesk releases an official patch; consider deploying file sandboxing or endpoint protection to block malicious file execution.

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:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad ArchitectureApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad ElectricalApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad MechanicalApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad MepApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad Plant 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Civil 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Advance SteelApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.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 and version
    Open Windows Settings > Apps & Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName, DisplayVersion' in PowerShell to list installed Autodesk applications and their versions.
    Affected if The installed version falls within any of these ranges: >= 2021 but < 2021.1.4; >= 2022 but < 2022.1.4; >= 2023 but < 2023.1.5; >= 2024 but < 2024.1.3; >= 2025 but < 2025.0.1
  2. Locate vulnerable DLL files
    Search for ODXSW_DLL.dll and libodxdll.dll in the Autodesk application installation directory, typically found under C:\Program Files\Autodesk\ or C:\Program Files (x86)\Autodesk\
    Affected if Either ODXSW_DLL.dll or libodxdll.dll exists in the application directory, indicating the vulnerable component is present
  3. Check ODX import functionality
    In the Autodesk application, access the Insert tab or File > Open to see if ODX, SLDPRT, or SLDASM file import options are available. The vulnerability triggers when parsing these file types.
    Affected if The application can open or import MODEL, SLDPRT, or SLDASM files, meaning the parsing code path that contains the flaw is reachable

You are affected if you have an Autodesk product version within the ranges listed and the vulnerable DLL files exist, especially if users open or import MODEL, SLDPRT, or SLDASM 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 2021.1.4 / 2022.1.4 / 2023.1.5 or later
Fixed in 2021.1.42022.1.42023.1.5
Interim mitigation

Avoid opening untrusted MODEL, SLDPRT, or SLDASM files until Autodesk releases an official patch; consider deploying file sandboxing or endpoint protection to block malicious file execution.

Recommended fix High confidence

2021.1.4 (for 2021 line), 2022.1.4 (for 2022 line), 2023.1.5 (for 2023 line), 2024.1.3 (for 2024 line)

  1. Identify the specific Autodesk product (e.g., AutoCAD, Civil 3D, Advance Steel) and current version installed in the environment
  2. Determine which release line the installed version belongs to (2021, 2022, 2023, or 2024)
  3. If version is >= 2021 and < 2021.1.4, upgrade to version 2021.1.4 or later
  4. If version is >= 2022 and < 2022.1.4, upgrade to version 2022.1.4 or later
  5. If version is >= 2023 and < 2023.1.5, upgrade to version 2023.1.5 or later
  6. If version is >= 2024 and < 2024.1.3, upgrade to version 2024.1.3 or later
  7. Obtain the update from the official Autodesk website or your organization's software distribution channel
  8. Apply the update following standard Autodesk installation procedures
Caveat Standard Autodesk update considerations apply - ensure compatibility with custom scripts, plugins, and dependent workflows before deployment

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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