CVE-2024-12194
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 · uneditedA maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to 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 confidenceA memory corruption vulnerability exists in Autodesk Navisworks when parsing maliciously crafted DWFX files. The vulnerability allows arbitrary code execution in the context of the current process, likely due to improper bounds checking or memory allocation during DWFX file parsing.
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>= 2025, < 2025.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Navisworks installationCheck for Navisworks installation by searching Program Files or querying the Windows Registry under HKLM\SOFTWARE\Autodesk\NavisworksAffected if Navisworks is present on the system
-
Identify installed Navisworks versionLocate the Navisworks executable (typically in C:\Program Files\Autodesk\Navisworks Manage 2025\ or similar) and check its properties, or query the registry key for the installed version stringAffected if Installed version falls within >= 2025 and < 2025.4
-
Confirm DWFX file associationCheck if Navisworks has registered handlers for .dwfx files by examining Registry entries under HKCR\.dwfx or by attempting to open a DWFX file with NavisworksAffected if DWFX file types are associated with Navisworks and the software can parse these files
-
Review application crash logsExamine Windows Event Viewer Application logs and any Navisworks-specific log directories for recent crash events or error entries related to DWFX file parsingAffected if Recent crashes or errors logged when processing DWFX files
A system is affected if Navisworks version 2025.0 through 2025.3.x is installed and the DWFX parsing capability is available or has been used.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2025.4
Avoid opening untrusted DWFX files in Navisworks until a vendor patch is available. Apply the principle of least privilege to limit the impact of potential code execution.
Navisworks 2025.4
- 1. Close any running instances of Autodesk Navisworks 2025
- 2. Download Autodesk Navisworks 2025.4 or later from the official Autodesk website (https://www.autodesk.com/products/navisworks/overview)
- 3. Run the installer and follow the on-screen prompts to install the update
- 4. After installation, verify the version by opening Navisworks and checking Help > About Autodesk Navisworks
- 5. Confirm the version displayed is 2025.4 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12194 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12194 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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