dbcve.org
RevitApplication · Autodesk

CVE-2024-11608

HIGH · 7.8 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 2023.1.7 / 2024.3.2 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 SKP file, when linked or imported into Autodesk Revit, can be used to cause a Heap-based Overflow. 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 · moderate confidence

A heap-based buffer overflow vulnerability exists in Autodesk Revit's SKP file import functionality. When the software parses a maliciously crafted SketchUp (SKP) file during linked or imported operations, it fails to properly validate buffer boundaries, allowing an attacker to overwrite heap memory and potentially execute arbitrary code in the context of the current process.

MitigationOrganizations should avoid opening or importing SKP files from untrusted or unknown sources until Autodesk releases an official patch. If possible, implement file type restrictions and sandbox environments for handling untrusted CAD files.

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
RevitApplication
Affected:>= 2023, < 2023.1.7>= 2024, < 2024.3.2>= 2025, < 2025.4

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. Verify Autodesk Revit is installed
    Check for Revit installation by looking in standard program directories (e.g., C:\Program Files\Autodesk\Revit 202X) or by running 'where revit.exe' in Command Prompt
    Affected if Revit is not installed on the system
  2. Identify installed Revit version
    Open Revit, go to Help > About Autodesk Revit, or check the executable properties ofRevit.exe in the installation folder to read the file version
    Affected if The version falls within any of these ranges: 2023.0 to 2023.1.6, 2024.0 to 2024.3.1, or 2025.0 to 2025.3
  3. Confirm SKP import functionality is accessible
    In Revit, attempt to access the Import or Link workflow (Insert tab > Link CAD or Import) and verify that .skp (SketchUp) file type appears in the supported format dropdown
    Affected if SKP file format is listed as an available import option and the user has permissions to use CAD link/import features
  4. Check for recent SKP file operations
    Review Revit project logs (located in %LOCALAPPDATA%\Autodesk\Revit\Revit<version>\Logs) or Windows Event Viewer for evidence of recent .skp file imports or links
    Affected if SKP import or link operations have been performed on the system using an affected version

You are affected if Autodesk Revit is installed with a version in the ranges 2023.0-2023.1.6, 2024.0-2024.3.1, or 2025.0-2025.3, and the SKP file import/link feature is accessible or has been used.

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 2023.1.7 / 2024.3.2 / 2025.4 or later
Fixed in 2023.1.72024.3.22025.4
Interim mitigation

Organizations should avoid opening or importing SKP files from untrusted or unknown sources until Autodesk releases an official patch. If possible, implement file type restrictions and sandbox environments for handling untrusted CAD files.

Recommended fix High confidence

Revit 2023.1.7 or later; Revit 2024.3.2 or later; Revit 2025.4 or later

  1. Identify the currently installed Autodesk Revit version by opening Revit and navigating to Help > About Autodesk Revit
  2. Determine which version range your current installation falls into (2023, 2024, or 2025)
  3. Download the appropriate fixed release from the Autodesk Account portal or official Autodesk support website: For Revit 2023, download version 2023.1.7 or later; For Revit 2024, download version 2024.3.2 or later; For Revit 2025, download version 2025.4 or later
  4. Close all running instances of Autodesk Revit before installing the update
  5. Run the installer with administrative privileges and follow the on-screen installation prompts
  6. Restart the computer after the installation completes
  7. Verify the installed version by opening Revit and checking Help > About Autodesk Revit to confirm the version matches the fixed release
  8. Test that importing or linking SKP files works correctly in the updated version
Caveat Minor: Patch releases typically maintain compatibility, but verify that existing project files and any integrated plugins work with the new version before production use

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

Fix this in Revit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
27.0 hours of engineering $4,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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