dbcve.org
AutocadApplication · Autodesk

CVE-2024-23153

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 MODEL file, when parsed in libodx.dll through Autodesk applications, can force an Out-of-Bounds 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 · moderate confidence

A vulnerability in libodx.dll allows parsing of maliciously crafted MODEL files to trigger an out-of-bounds read, potentially enabling denial of service, information disclosure, or arbitrary code execution in the context of the current process.

MitigationAvoid opening untrusted or unsolicited MODEL files. Apply vendor patches for affected Autodesk applications when available.

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
    Check Add/Remove Programs or the Program Files directory for Autodesk applications such as AutoCAD, Civil 3D, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, or AutoCAD Plant 3D.
    Affected if Any of the affected Autodesk products listed in the CVE is installed on the system
  2. Check installed product version
    Open the Autodesk application and go to Help > About to view the version number, or look in Add/Remove Programs. Compare the version against the affected ranges: 2022.x before 2022.1.5, 2023.x before 2023.1.6, 2024.x before 2024.1.5, or 2025.x before 2025.1.
    Affected if The installed version falls within any of the vulnerable version ranges (2022 through 2025, with versions below the patched releases)
  3. Locate libodx.dll
    Search for libodx.dll in the product installation directory, typically found under C:\Program Files\Autodesk\[ProductName]\bin\ or the application's root folder.
    Affected if libodx.dll exists in the Autodesk product installation directory, indicating the vulnerable component is present

The environment is affected if an Autodesk product from the affected list is installed with a version matching the vulnerable ranges and the libodx.dll component is present, allowing parsing of MODEL files to trigger the out-of-bounds read.

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

Avoid opening untrusted or unsolicited MODEL files. Apply vendor patches for affected Autodesk applications when available.

Recommended fix High confidence

Minimum fixed versions: 2022.1.5, 2023.1.6, 2024.1.5, or 2025.1 (depending on your release cycle)

  1. Identify the specific Autodesk product and version currently installed (2022, 2023, 2024, or 2025)
  2. For AutoCAD 2022: upgrade to version 2022.1.5 or later
  3. For AutoCAD 2023: upgrade to version 2023.1.6 or later
  4. For AutoCAD 2024: upgrade to version 2024.1.5 or later
  5. For AutoCAD 2025: upgrade to version 2025.1 or later
  6. Apply the same version upgrades to any affected vertical products (Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, Civil 3D) if installed
  7. Verify the installation by checking Help > About Autodesk [Product] to confirm the version number
Caveat Review Autodesk's release notes for your specific version upgrade to check for any workflow changes or deprecated features

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

Fix this in Autocad Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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