dbcve.org
NavisworksApplication · Autodesk

CVE-2024-12669

HIGH · 7.8 CVSS v3.1 Published 2024-12-17
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 DWFX file, when parsed through Autodesk Navisworks, can be used to cause a Heap-based Overflow 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 · moderate confidence

A heap-based buffer overflow vulnerability exists in Autodesk Navisworks when parsing maliciously crafted DWFX files. The overflow allows a remote attacker to potentially execute arbitrary code in the context of the current process by triggering the overflow through a specially constructed file.

MitigationAvoid opening untrusted DWFX files in Autodesk Navisworks and apply vendor security updates when available. Implement file origin restrictions and user training on file source verification.

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
NavisworksApplication
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. Check if Autodesk Navisworks is installed
    Look for Navisworks in the installed programs list. On Windows, check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or inspect the program files directory (typically C:\Program Files\Autodesk\Navisworks).
    Affected if Autodesk Navisworks is found on the system
  2. Determine the installed Navisworks version
    Right-click the Navisworks executable (usually NwMaster.exe or similar) in the installation folder, select Properties, then go to the Details tab to view the Product version. Alternatively, open Navisworks and go to Help > About Autodesk Navisworks to see the full version number.
    Affected if The version displayed is 2025.x where x is less than 2025.4 (e.g., 2025.0, 2025.1, 2025.2, 2025.3)
  3. Verify DWFX file support is enabled
    Check Navisworks options: go to Application menu > Options > File Reader or check the file import settings. Confirm DWFX/DWF is listed as an enabled format. This is typically enabled by default.
    Affected if DWFX file reading is enabled (default state)
  4. Check for recent DWFX file processing activity
    Review recent files opened in Navisworks (File > Recent) or check the application log files in %APPDATA%\Autodesk\Navisworks for entries involving .dwfx files.
    Affected if Users have recently opened DWFX files from untrusted sources

A system is affected if Autodesk Navisworks version 2025.x (where x < 2025.4) is installed and DWFX file parsing is enabled, which is the default configuration.

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 untrusted DWFX files in Autodesk Navisworks and apply vendor security updates when available. Implement file origin restrictions and user training on file source verification.

Recommended fix High confidence

Navisworks 2025.4

  1. Backup any important Navisworks projects and configurations before updating
  2. Download Autodesk Navisworks 2025.4 (or later) from the official Autodesk website (www.autodesk.com)
  3. Close all running instances of Navisworks
  4. Run the installer for Navisworks 2025.4 and follow the on-screen prompts to complete the upgrade
  5. After installation, launch Navisworks and verify that the application runs without errors
  6. Test with DWFX files to confirm the vulnerability is resolved

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

Fix this in Navisworks Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,820
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,912.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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