dbcve.org
NavisworksApplication · Autodesk

CVE-2024-12200

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 DWFX files. A maliciously crafted DWFX file can trigger the software to write data beyond allocated memory boundaries, potentially allowing arbitrary code execution, crashes, or data corruption in the context of the current process.

MitigationAvoid opening untrusted or unverified DWXY files in Autodesk Navisworks until an official vendor patch is applied. Implement file validation and sandboxing as additional layers of defense.

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. Verify Autodesk Navisworks installation
    Check if Autodesk Navisworks is installed on the system. This can be done by looking in the Windows Programs and Features list, or by searching for Navisworks in the Start menu or Program Files directory.
    Affected if Navisworks is present on the system
  2. Identify installed Navisworks version
    Open Navisworks and navigate to Help > About Autodesk Navisworks, or check the version in the Windows Programs and Features list under the installed Navisworks entry.
    Affected if Unable to determine the version number
  3. Compare version against affected range
    Compare the installed version number to the affected range: version 2025.0 through 2025.3.x are vulnerable. Versions below 2025 and versions 2025.4 and later are not affected.
    Affected if Installed version is 2025.0 or higher but lower than 2025.4
  4. Assess DWFX file handling exposure
    Determine whether the Navisworks installation routinely opens DWFX files from external or untrusted sources, as this is the attack vector for triggering the vulnerability.
    Affected if Navisworks is used to open DWFX files from untrusted or unknown sources

The environment is affected if Autodesk Navisworks version 2025.0 through 2025.3.x is installed and users open DWFX files, since the out-of-bounds write occurs during DWFX file 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

Avoid opening untrusted or unverified DWXY files in Autodesk Navisworks until an official vendor patch is applied. Implement file validation and sandboxing as additional layers of defense.

Recommended fix High confidence

Navisworks 2025.4

  1. Check the current version of Autodesk Navisworks by opening the application and navigating to Help > About Autodesk Navisworks
  2. Visit the official Autodesk support or download page at www.autodesk.com to obtain Navisworks version 2025.4 or later
  3. Download the updated Navisworks installer for your specific version (2025)
  4. Run the installer and follow the on-screen prompts to apply the update
  5. Restart the application after the update completes
  6. Verify the installed version shows 2025.4 or later

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

Fix this in Navisworks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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