dbcve.org
AutocadApplication · Autodesk

CVE-2024-9827

HIGH · 7.8 CVSS v3.1 Published 2024-10-29
Fix available
A fix is available. Upgrade to 2025.1.1 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 CATPART file when parsed in CC5Dll.dll through Autodesk AutoCAD can force an Out-of-Bounds Read vulnerability. 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 · high confidence

A maliciously crafted CATPART file parsed by the CC5Dll.dll library in Autodesk AutoCAD triggers an out-of-bounds read vulnerability. An attacker can exploit this to cause a denial-of-service (application crash), read sensitive memory contents, or potentially achieve arbitrary code execution within the current process context.

MitigationApply the vendor-provided security patch from Autodesk to address the vulnerability in CC5Dll.dll. Until patched, avoid opening untrusted or unfamiliar CATPART files from unknown sources, and consider running AutoCAD in an isolated environment to limit potential impact.

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:>= 2025, < 2025.1.1
Autocad Advance SteelApplication
Affected:>= 2025, < 2025.1.1
Autocad ArchitectureApplication
Affected:>= 2025, < 2025.1.1
Autocad Civil 3dApplication
Affected:>= 2025, < 2025.1.1
Autocad ElectricalApplication
Affected:>= 2025, < 2025.1.1
Autocad MechanicalApplication
Affected:>= 2025, < 2025.1.1
Autocad MepApplication
Affected:>= 2025, < 2025.1.1
Autocad Plant 3dApplication
Affected:>= 2025, < 2025.1.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 AutoCAD product version
    Open AutoCAD and go to Help > About Autodesk AutoCAD, or run the 'VER' or 'SETVER' command in the command line. Alternatively, locate the acad.exe file in the installation directory and check its file properties for version information.
    Affected if The installed version is AutoCAD 2025.x where x is any version prior to 2025.1.1, or any of the listed vertical products (Advance Steel, Architecture, Civil 3D, Electrical, Mechanical, MEP, Plant 3D) at version 2025.x prior to 2025.1.1.
  2. Locate the vulnerable CC5Dll.dll library
    Search for the file CC5Dll.dll within the AutoCAD installation directory. Common paths include the base installation folder or subfolders such as 'C:\Program Files\Autodesk\AutoCAD 2025\' or product-specific subdirectories.
    Affected if The file CC5Dll.dll exists in the AutoCAD installation directory, indicating the component that contains the vulnerability is present.
  3. Confirm CATPART file import capability
    Check if the CATPART file import feature is available. In AutoCAD, attempt to use the IMPORT command or look for CATIA or CATPART-related import options under the Insert tab or in the available import/export file type filters.
    Affected if CATPART file import functionality is present and enabled, meaning the vulnerable parsing code path can be triggered by opening a specially crafted file.
  4. Verify AutoCAD is configured to handle CATPART files
    Check the supported file extensions in AutoCAD's options (OP command) under the Files tab, or examine any registered file handlers for .catpart extension in the system registry under HKEY_CLASSES_ROOT\.catpart.
    Affected if The system has file associations or handlers registered for .catpart files that would cause AutoCAD to attempt parsing when such a file is opened.

A user is affected if they have any of the listed AutoCAD 2025 products installed with a version lower than 2025.1.1, the CC5Dll.dll library is present, and CATPART file import functionality is available or enabled.

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 2025.1.1 or later
Fixed in 2025.1.1
Interim mitigation

Apply the vendor-provided security patch from Autodesk to address the vulnerability in CC5Dll.dll. Until patched, avoid opening untrusted or unfamiliar CATPART files from unknown sources, and consider running AutoCAD in an isolated environment to limit potential impact.

Recommended fix High confidence

AutoCAD 2025.1.1 (or later) - applies to all affected product variants

  1. Open Autodesk AutoCAD or one of the affected vertical products (Advance Steel, Architecture, Civil 3D, Electrical, Mechanical, MEP, or Plant 3D)
  2. Navigate to the Help menu and select 'About Autodesk AutoCAD' to verify the current version number
  3. Ensure the current version is >= 2025 and < 2025.1.1 to confirm the system is vulnerable
  4. Visit the official Autodesk support website at www.autodesk.com or your Autodesk Account portal
  5. Locate and download the AutoCAD 2025.1.1 (or later) update for your specific product variant
  6. Run the installer with administrator privileges and follow the on-screen prompts to apply the update
  7. Restart the application after the update completes
  8. Verify the installed version shows 2025.1.1 or later by checking Help > About
Caveat Minor: Standard update; review Autodesk release notes for any workflow changes in 2025.1.1

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

Fix this in Autocad Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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