CVE-2024-12178
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 · high confidenceA memory corruption vulnerability exists in Autodesk Navisworks when parsing maliciously crafted DWFX files. The vulnerability allows a remote attacker to execute arbitrary code in the context of the current process by tricking a user into opening a specially designed DWFX file.
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.
-
Check if Autodesk Navisworks is installedLook for Navisworks in the list of installed programs via Windows Settings > Apps & Features, or check for Navisworks executable in Program FilesAffected if Navisworks is not installed on the system, then the CVE does not apply
-
Determine the installed Navisworks versionRight-click the Navisworks executable (typically nvw or similar) and select Properties > Details to view the File Version, or use the application's Help > About dialogAffected if Unable to determine version, making it unclear whether the installation is affected
-
Compare installed version against affected rangeCheck if the version falls within >= 2025 and < 2025.4 (such as 2025.0, 2025.1, 2025.2, 2025.3)Affected if Installed version is 2025.0 through 2025.3.x, meaning the version is vulnerable
-
Assess exposure to untrusted DWFX filesDetermine whether users in the environment commonly open DWFX files from external or untrusted sources, or if file preview handlers are activeAffected if Users routinely open DWFX files from untrusted sources and the version is within the affected range
The environment is affected if Autodesk Navisworks version 2025.0 through 2025.3.x is installed and users can open DWFX files from untrusted sources.
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
Apply the vendor patch when released by Autodesk; until then, exercise extreme caution with DWFX files from untrusted sources and consider disabling file preview functionality in Navisworks.
Navisworks 2025.4
- Upgrade Autodesk Navisworks to version 2025.4 or later
- Verify the upgrade was successful by checking the application version
- After upgrading, reopen and re-validate any DWFX files that were previously parsed with the vulnerable version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12178 — 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-12178 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