dbcve.org
Autocad ElectricalApplication · Autodesk

CVE-2024-23122

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 3DM file, when parsed in opennurbs.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

A maliciously crafted 3DM file parsed in opennurbs.dll within Autodesk AutoCAD triggers an out-of-bounds write vulnerability. This memory corruption can be leveraged by an attacker to crash the application, corrupt data, or achieve arbitrary code execution in the context of the current process.

MitigationApply the vendor-supplied patch for Autodesk AutoCAD when available. Until then, avoid opening 3DM files from untrusted sources.

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 the installed AutoCAD product variant
    Open AutoCAD and go to Help > About Autodesk AutoCAD, or check the installed programs list in Windows Control Panel. Look for the product name (AutoCAD, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, Advance Steel, or AutoCAD Map 3D).
    Affected if The product is any of these eight variants: AutoCAD, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, Advance Steel, or AutoCAD Map 3D.
  2. Determine the installed software version
    In AutoCAD, type VER at the command line and press Enter, or check Help > About. Note the full version number (for example: 2021.1, 2022.0, 2023.1.4, etc.).
    Affected if The version falls within any of these ranges: 2021.0 to 2021.1.3, 2022.0 to 2022.1.3, 2023.0 to 2023.1.4, 2024.0 to 2024.1.2, or 2025.0.
  3. Verify if 3DM file handling is available
    Check if the opennurbs.dll library exists in the installation directory (typically in the Support folder under the AutoCAD installation path). Attempt to open any .3dm file or check recent file history.
    Affected if The opennurbs.dll file is present and the user has opened or could open 3DM files.
  4. Confirm the opennurbs.dll version
    Locate opennurbs.dll in the AutoCAD installation folder, right-click the file, select Properties, and view the File Version field on the Details tab.
    Affected if The file version is earlier than the patched version corresponding to the release (prior to 2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, or 2025.0.1 for their respective release).

The environment is affected if any of the eight AutoCAD variants is installed with a version between 2021.0 and the patched release numbers, and the opennurbs.dll component handles 3DM 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

Apply the vendor-supplied patch for Autodesk AutoCAD when available. Until then, avoid opening 3DM files from untrusted sources.

Recommended fix High confidence

Upgrade to version 2021.1.4 (for 2021 line), 2022.1.4 (for 2022 line), 2023.1.5 (for 2023 line), or 2024.1.3 (for 2024 line) depending on your current major version

  1. Identify the currently installed Autodesk product and version (e.g., AutoCAD 2023, Civil 3D 2024, etc.)
  2. Determine the appropriate fixed version based on your product line: for 2021.x upgrade to 2021.1.4, for 2022.x upgrade to 2022.1.4, for 2023.x upgrade to 2023.1.5, for 2024.x upgrade to 2024.1.3
  3. Download the update from the official Autodesk website or through your Autodesk Account portal
  4. Close all instances of the affected Autodesk application before applying the update
  5. Run the installer and follow the on-screen prompts to apply the update
  6. Restart the application after the update completes
  7. Verify the installed version matches the target fixed release
Caveat Patch releases typically contain only security and critical bug fixes with minimal risk; however, verify that any custom scripts or third-party extensions are compatible with the new version before deploying broadly

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

Fix this in Autocad Electrical 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-23122 — 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-23122 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