NavisworksApplication · Autodesk

CVE-2022-25796

HIGH · 7.8 CVSS v3.1 Published 2022-04-11
Fix available
A fix is available. Upgrade to 2022.2 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 Double Free vulnerability allows remote malicious actors to execute arbitrary code on DWF file in Autodesk Navisworks 2022 within affected installations. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

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 confidence

A double-free vulnerability in Autodesk Navisworks 2022 when parsing malicious DWF files allows remote attackers to execute arbitrary code on affected systems. The vulnerability requires user interaction—specifically opening a crafted malicious DWF file—to trigger the double-free condition.

MitigationApply the vendor patch or update to a fixed version of Autodesk Navisworks 2022. Until patched, users should not open DWF files from untrusted sources.

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:>= 2022, < 2022.2

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 2022 is installed
    Check for Navisworks 2022 in the Windows installed programs list (Control Panel > Programs and Features) or look for the application in the default install location typically at C:\Program Files\Autodesk\Navisworks Manage 2022\ or C:\Program Files (x86)\Autodesk\Navisworks Manage 2022\
    Affected if Autodesk Navisworks 2022 is present on the system
  2. Determine the installed version number
    Open Navisworks and go to Help > About, or right-click the executable (NwView.exe, Nu舞.exe, or similar) in the install folder and view Properties > Details to find the File Version. Compare this version against the affected range (2022.0.0 through 2022.1.x)
    Affected if Installed version is 2022.0.0 through 2022.1.x (anything less than 2022.2)
  3. Check for DWF file handling capability
    Verify the DWF importer module exists in the Navisworks installation folder - look for DWF-related DLLs such as DwfReader.dll or similar DWF parsing components in the bin folder
    Affected if DWF parsing modules are present and loaded by Navisworks
  4. Review recent DWF file access
    Check Windows Event Viewer for recent DWF file opens, or search the user's recent documents and the Navisworks project history for DWF files opened from untrusted sources
    Affected if DWF files from untrusted sources have been opened recently using Navisworks 2022

System is affected if Autodesk Navisworks 2022 version 2022.0.0 through 2022.1.x is installed and the DWF file parsing feature is present and has been used to open files.

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 2022.2 or later
Fixed in 2022.2
Interim mitigation

Apply the vendor patch or update to a fixed version of Autodesk Navisworks 2022. Until patched, users should not open DWF files from untrusted sources.

Recommended fix High confidence

Navisworks 2022.2

  1. Download Autodesk Navisworks 2022.2 from the official Autodesk website (www.autodesk.com)
  2. Install the update following Autodesk's standard installation procedures
  3. Verify the installation completed successfully by checking the version number

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

Fix this in Navisworks Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25796 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25796 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