dbcve.org
NavisworksApplication · Autodesk

CVE-2024-12197

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, may force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, 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

An out-of-bounds write vulnerability exists in Autodesk Navisworks when parsing maliciously crafted DWFX files. The vulnerability occurs due to insufficient bounds checking during DWFX file parsing, allowing a specially crafted file to write beyond allocated memory boundaries. This can result in process crash, memory corruption, or potential arbitrary code execution within the context of the running Navisworks application.

MitigationUsers should avoid opening DWFX files from untrusted or unknown sources. Organizations should implement file vetting procedures and monitor for vendor patches for Autodesk Navisworks that address this vulnerability.

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. Identify installed Navisworks version
    Open Windows Programs and Features (appwiz.cpl), or right-click the Navisworks executable and select Properties > Details to view the version number
    Affected if Version shows 2025.x where x is 0, 1, 2, or 3 (any version from 2025.0 through 2025.3)
  2. Confirm exact version string
    In Programs and Features, locate Autodesk Navisworks 2025 and note the full version number displayed in the Version column
    Affected if Version string begins with 2025.0, 2025.1, 2025.2, or 2025.3 (versions prior to 2025.4)
  3. Check for DWFX file handling
    Navisworks parses DWFX files when users open or import files with .dwfx extension; verify if your workflow involves opening DWFX files
    Affected if You routinely open or import DWFX files from external or untrusted sources

You are affected if Navisworks 2025.0 through 2025.3 is installed and you open DWFX files, since the vulnerability triggers during DWFX parsing in these versions.

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

Users should avoid opening DWFX files from untrusted or unknown sources. Organizations should implement file vetting procedures and monitor for vendor patches for Autodesk Navisworks that address this vulnerability.

Recommended fix High confidence

Navisworks 2025.4

  1. 1. Back up all current project files and Navisworks user settings before proceeding with the upgrade
  2. 2. Uninstall the current version of Autodesk Navisworks 2025 (any version prior to 2025.4)
  3. 3. Download Navisworks 2025.4 or later from the official Autodesk website (https://www.autodesk.com/products/navisworks/overview)
  4. 4. Run the installer with administrator privileges
  5. 5. Follow the installation wizard prompts to complete the installation
  6. 6. After installation, verify the version by opening Navisworks and checking Help > About Autodesk Navisworks
  7. 7. Test with legitimate DWFX files to ensure functionality is intact
Caveat Review Autodesk release notes for 2025.4 for any feature changes or workflow adjustments before deploying in production

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

Fix this in Navisworks Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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