dbcve.org
AutocadApplication · Autodesk

CVE-2024-23148

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 CATPRODUCT file, when parsed in CC5Dll.dll through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, in conjunction with other vulnerabilities, can lead to code execution 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 memory corruption vulnerability exists in CC5Dll.dll when parsing maliciously crafted CATPRODUCT files in Autodesk applications. The flaw manifests as a write access violation during file parsing, which when combined with other vulnerabilities can enable code execution in the current process context.

MitigationApply the vendor security update from Autodesk to patch the vulnerable CC5Dll.dll component. Avoid opening untrusted CATPRODUCT files from unknown or untrusted sources until patches are 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
AutocadApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad ArchitectureApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad ElectricalApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad Map 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad MechanicalApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad MepApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad Plant 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Civil 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 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 Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*AutoCAD*' -or $_.DisplayName -like '*Civil*'}
    Affected if No Autodesk product from the affected list is installed (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D)
  2. Determine the installed version
    In Programs and Features, locate the Autodesk product and note the version number (for example 2022, 2023, 2024, or 2025). Alternatively, right-click the main executable (such as acad.exe) in the installation folder, select Properties, and check the File Version tab.
    Affected if The installed version cannot be determined or does not match the year-based versioning (2022, 2023, 2024, or 2025)
  3. Compare version against affected ranges
    Match the installed version year and full version number against these vulnerable ranges: 2022 versions before 2022.1.5; 2023 versions before 2023.1.6; 2024 versions before 2024.1.4; 2025 versions before 2025.1
    Affected if The installed version falls within any of these ranges: >= 2022 and < 2022.1.5; >= 2023 and < 2023.1.6; >= 2024 and < 2024.1.4; >= 2025 and < 2025.1
  4. Locate the vulnerable component
    Search for CC5Dll.dll in the application installation directory. Common paths include C:\Program Files\Autodesk\AutoCAD [VERSION]\ or C:\Program Files\Autodesk\Civil 3D [VERSION]\. Use PowerShell: Get-ChildItem -Path 'C:\Program Files\Autodesk' -Recurse -Filter 'CC5Dll.dll' -ErrorAction SilentlyContinue
    Affected if CC5Dll.dll is present in the Autodesk installation directory
  5. Verify CATPRODUCT file handling capability
    Check if the application has the capability to import or open CATPRODUCT files. This is typically indicated by available import filters or by examining file association settings for .catproduct extensions within the Autodesk application.
    Affected if CATPRODUCT file import or processing features are available and enabled in the application

You are affected if you have any of the listed Autodesk products installed with a version within the vulnerable ranges (2022 < 2022.1.5, 2023 < 2023.1.6, 2024 < 2024.1.4, or 2025 < 2025.1) and the CC5Dll.dll component is present on your system.

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.4 or later
Fixed in 2022.1.52023.1.62024.1.4
Interim mitigation

Apply the vendor security update from Autodesk to patch the vulnerable CC5Dll.dll component. Avoid opening untrusted CATPRODUCT files from unknown or untrusted sources until patches are applied.

Recommended fix High confidence

Upgrade to minimum fixed versions: AutoCAD/AutoCAD-based products 2022.1.5+, 2023.1.6+, 2024.1.4+, or 2025.1+

  1. 1. Identify the specific Autodesk product (e.g., AutoCAD, AutoCAD Architecture, Civil 3D, etc.) and current version installed in your environment
  2. 2. Determine which version branch your installation belongs to (2022, 2023, 2024, or 2025)
  3. 3. For version 2022: Upgrade to version 2022.1.5 or later
  4. 4. For version 2023: Upgrade to version 2023.1.6 or later
  5. 5. For version 2024: Upgrade to version 2024.1.4 or later
  6. 6. For version 2025: Upgrade to version 2025.1 or later
  7. 7. Download the appropriate update from the official Autodesk website (www.autodesk.com) or use the Autodesk Desktop App for automatic updates
  8. 8. Apply the update following standard Autodesk installation procedures
Caveat Standard Autodesk update considerations apply - review release notes for compatibility notes with custom scripts, plugins, or older file formats

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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