dbcve.org
RevitApplication · Autodesk

CVE-2024-11454

HIGH · 7.8 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 2025.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 DLL file, when placed in the same directory as an RVT file could be loaded by Autodesk Revit, and execute arbitrary code in the context of the current process due to an untrusted search patch being utilized.

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

Autodesk Revit is vulnerable to DLL hijacking via an untrusted search path. When opening an RVT file from a directory containing a maliciously crafted DLL with a name Revit expects, the application loads and executes arbitrary code in the current process context.

MitigationAvoid opening RVT files from untrusted or shared directories. Remove or quarantine any unexpected DLL files in directories containing RVT files until Autodesk releases an official patch addressing the insecure DLL loading.

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:>= 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. Identify installed Revit version
    Open Revit, go to Help > About Autodesk Revit, or check Add/Remove Programs in Control Panel for the version number
    Affected if Version is 2025.x where x is less than 4 (any version from 2025.0 through 2025.3)
  2. Locate directories where you store or receive RVT files
    Search your file system for .rvt files, or identify common folders where team members place RVT files for sharing
    Affected if You have RVT files in shared network directories, download folders, or other locations accessible to untrusted users
  3. Inspect RVT file directories for unexpected DLL files
    Examine each directory containing RVT files for any DLL files that are not clearly part of a known Revit installation or add-in
    Affected if Any DLL file exists in a directory containing RVT files that was not placed there intentionally by your IT or BIM team
  4. Check current working directory behavior when opening RVT files
    Note the directory from which you typically double-click or open RVT files; verify whether Revit loads DLLs from that same directory
    Affected if You open RVT files by double-clicking from directories that may contain untrusted files, or Revit loads DLLs from the directory containing the opened RVT file

You are affected if you run any Autodesk Revit version 2025.0 through 2025.3 and open RVT files from directories that could contain malicious DLLs.

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

Avoid opening RVT files from untrusted or shared directories. Remove or quarantine any unexpected DLL files in directories containing RVT files until Autodesk releases an official patch addressing the insecure DLL loading.

Recommended fix High confidence

Revit 2025.4 or later

  1. Check the current installed version of Autodesk Revit (Help > About Autodesk Revit)
  2. Back up all critical RVT project files and user settings before upgrading
  3. Download Autodesk Revit 2025.4 (or later) from the official Autodesk website (www.autodesk.com) or your Autodesk Account portal
  4. Close all running instances of Autodesk Revit
  5. Run the installer with administrator privileges
  6. Follow the on-screen installation prompts to complete the upgrade
  7. Verify the installation was successful by checking Help > About Autodesk Revit shows version 2025.4 or later
Caveat Standard upgrade; review Autodesk release notes for any workflow or API changes specific to 2025.4

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

Fix this in Revit Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,460
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,336.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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