dbcve.org
AutocadApplication · Autodesk

CVE-2024-23150

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 PRT file, when parsed in odxug_dll.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 PRT file parsed through odxug_dll.dll in Autodesk AutoCAD triggers an out-of-bounds write vulnerability, which can lead to crashes, data corruption, or arbitrary code execution within the current process context.

MitigationApply the vendor security patch from Autodesk when released; until then, avoid opening untrusted or unknown PRT files in AutoCAD.

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
    Open AutoCAD and type 'ABOUT' in the command line, or check Programs and Features in Control Panel to see which Autodesk product is installed (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D)
    Affected if The product is any of the eight listed Autodesk products listed in the affected versions
  2. Check product version
    In AutoCAD, type 'VER' or 'ABOUT' at the command prompt to display the version and build number. Compare against the affected ranges: 2022 versions before 2022.1.5, 2023 versions before 2023.1.6, 2024 versions before 2024.1.5, or 2025 versions before 2025.1
    Affected if The installed version falls within any of these ranges: >=2022,<2022.1.5 OR >=2023,<2023.1.6 OR >=2024,<2024.1.5 OR >=2025,<2025.1
  3. Locate odxug_dll.dll
    Search for odxug_dll.dll in the AutoCAD installation directory (typically C:\Program Files\Autodesk\<Product>\) and note its presence and version by right-clicking the file, selecting Properties, and viewing the Details tab
    Affected if The DLL exists in the AutoCAD installation folder, confirming the vulnerable component is present
  4. Check for recent PRT file processing
    Review recently opened files in AutoCAD (use the RECENTFILES command or check the Documents folder for .PRT files). Also check Windows Event Viewer for application crash events around the time of opening PRT files
    Affected if PR files from untrusted sources have been opened recently in the affected product version

You are affected if you have any of the eight Autodesk products installed (AutoCAD, Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, or Civil 3D) and the version falls within the affected ranges (2022 before 2022.1.5, 2023 before 2023.1.6, 2024 before 2024.1.5, or 2025 before 2025.1).

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

Apply the vendor security patch from Autodesk when released; until then, avoid opening untrusted or unknown PRT files in AutoCAD.

Recommended fix High confidence

Upgrade to AutoCAD 2022.1.5+, 2023.1.6+, 2024.1.5+, or 2025.1+ (depending on your product line)

  1. 1. Identify the exact version of installed Autodesk product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D) by opening the application and navigating to Help > About Autodesk AutoCAD.
  2. 2. Note the product year version (2022, 2023, 2024, or 2025) and current update release number.
  3. 3. Close all Autodesk applications completely.
  4. 4. Launch Autodesk Account or open the Autodesk Desktop App to check for available updates.
  5. 5. Download and install the appropriate update: For AutoCAD 2022.x users, install version 2022.1.5 or later; For AutoCAD 2023.x users, install version 2023.1.6 or later; For AutoCAD 2024.x users, install version 2024.1.5 or later; For AutoCAD 2025.x users, install version 2025.1 or later.
  6. 6. Alternatively, download updates directly from Autodesk's support website (https://www.autodesk.com/support) by searching for the specific product and version.
  7. 7. After installation, verify the update was successful by checking Help > About to confirm the patched version number.
  8. 8. Restart the application and test normal operations to ensure stability.
Caveat Standard Autodesk update - minimal risk; ensure backups of critical drawings before updating

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.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-23150 — 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-23150 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