dbcve.org
Autocad ElectricalApplication · Autodesk

CVE-2024-23121

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 file, when parsed in libodxdll.dll through Autodesk AutoCAD, may force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, 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 write vulnerability exists in libodxdll.dll when parsing MODEL files in Autodesk AutoCAD. Opening a maliciously crafted MODEL file can trigger memory corruption, potentially allowing an attacker to execute arbitrary code in the context of the current process.

MitigationApply the vendor patch from Autodesk to resolve the vulnerability in libodxdll.dll. Avoid opening MODEL files from untrusted or unknown sources until the patch 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
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
Autocad Map 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
AutocadApplication
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
    Check system for any of these affected applications: AutoCAD, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, Advance Steel, AutoCAD Map 3D. Look in typical installation paths such as C:\Program Files\Autodesk\ or use system inventory tools.
    Affected if Any of the listed Autodesk products are installed on the system
  2. Determine product version
    Open the installed Autodesk application and check the version (typically via Help > About or the application's properties), or locate the main executable and view its version properties. Common executables include acad.exe for AutoCAD, acade.exe for AutoCAD Electrical, etc.
    Affected if The installed version falls within these affected ranges: 2021 (prior to 2021.1.4), 2022 (prior to 2022.1.4), 2023 (prior to 2023.1.5), 2024 (prior to 2024.1.3), or 2025 (prior to 2025.0.1)
  3. Locate vulnerable DLL
    Search for libodxdll.dll in the application installation directory (typically under the bin folder within the product folder). Use file explorer or command: dir /s C:\Program Files\Autodesk\libodxdll.dll
    Affected if The DLL exists in the product installation directory, confirming the vulnerable component is present
  4. Confirm MODEL file interaction
    Identify if the system processes MODEL files (common in electrical/mechanical/Civil design workflows). Check for recent or active MODEL file operations in the application.
    Affected if Users open or process MODEL files within the affected AutoCAD-based product, which triggers the vulnerable code path in libodxdll.dll

You are affected if you have any of the listed Autodesk products installed with a version prior to the patched releases (2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, or 2025.0.1) AND users process MODEL files with that software.

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

Apply the vendor patch from Autodesk to resolve the vulnerability in libodxdll.dll. Avoid opening MODEL files from untrusted or unknown sources until the patch is applied.

Recommended fix High confidence

Upgrade to AutoCAD 2021.1.4+, 2022.1.4+, 2023.1.5+, or 2024.1.3+ (or respective versions for Electrical, Mechanical, MEP, Plant 3D, Civil 3D, Advance Steel, Map 3D)

  1. 1. Close any running Autodesk application (AutoCAD, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, Advance Steel, or AutoCAD Map 3D).
  2. 2. Ensure you have a backup of your current project files and settings.
  3. 3. Open a web browser and navigate to the Autodesk Account portal at accounts.autodesk.com.
  4. 4. Sign in with your Autodesk account credentials.
  5. 5. Navigate to the 'Products and Services' or 'All Products' section.
  6. 6. Locate your affected Autodesk product and click on the version number to expand available updates.
  7. 7. Download the appropriate update based on your current version: For 2021.x - download 2021.1.4 or later; For 2022.x - download 2022.1.4 or later; For 2023.x - download 2023.1.5 or later; For 2024.x - download 2024.1.3 or later.
  8. 8. Run the downloaded installer with administrator privileges.
Caveat Standard Autodesk service pack updates typically include bug fixes and security patches with minimal breaking changes; verify compatibility with custom scripts or third-party add-ins

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

Fix this in Autocad Electrical Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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