dbcve.org
NavisworksApplication · Autodesk

CVE-2024-12193

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

A memory corruption vulnerability exists in Autodesk Navisworks when parsing DWFX (Design Web Format) files. A maliciously crafted DWFX file can trigger an out-of-bounds write during parsing, allowing an attacker to overwrite adjacent memory locations. This can lead to process crash, data corruption, or potentially arbitrary code execution in the context of the current user process.

MitigationPrimary mitigation is applying Autodesk's official patch when available. In the interim, implement file-based input validation: scan DWFX files with endpoint protection, restrict Navisworks processing to trusted files only, and consider running Navisworks in sandboxed or isolated environments to limit blast radius if exploited.

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. Locate installed Autodesk Navisworks version
    Open Windows Control Panel > Programs and Features, or Windows Settings > Apps > Installed Apps, and locate Autodesk Navisworks in the list. Note the version number displayed.
    Affected if The version shown is 2025 (without update 2025.4 or later)
  2. Check Navisworks executable version via file properties
    Navigate to the Navisworks installation directory (typically C:\Program Files\Autodesk\Navisworks Manage 2025 or similar), right-click on the main executable (e.g., nwds.exe or Simulate.exe), select Properties, and view the Details tab for Product Version.
    Affected if The Product Version shows 2025.x where x is less than 2025.4, or shows only '2025' without a build number indicating the patched version
  3. Verify exact build number via registry
    Open Windows Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\Navisworks\2025 (or the relevant year key), and check the Release value or Version value for the exact build number.
    Affected if The build number is earlier than 2025.4 (the patched release)
  4. Confirm the vulnerability trigger condition
    This vulnerability is triggered specifically when Navisworks parses DWFX (Design Web Format) files. If your environment uses Navisworks to open or process DWFX files, the affected version is exploitable.
    Affected if Navisworks 2025 through 2025.3.x is installed and you process DWFX files with it

You are affected if Autodesk Navisworks 2025 (any build before 2025.4) is installed and you process DWFX files with it.

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

Primary mitigation is applying Autodesk's official patch when available. In the interim, implement file-based input validation: scan DWFX files with endpoint protection, restrict Navisworks processing to trusted files only, and consider running Navisworks in sandboxed or isolated environments to limit blast radius if exploited.

Recommended fix High confidence

Navisworks 2025.4

  1. Back up all existing Navisworks projects and settings before updating
  2. Navigate to the Autodesk Account or official Autodesk download page to obtain Navisworks 2025.4
  3. Download the Navisworks 2025.4 installer for your platform
  4. Run the installer and follow the on-screen prompts to complete the upgrade
  5. Launch Navisworks 2025.4 and verify that the application runs correctly
  6. Test with previously used DWFX files to ensure functionality is intact
Caveat Review the Autodesk Navisworks 2025.4 release notes for any feature changes or known issues before upgrading

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

Fix this in Navisworks Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
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,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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