FortiwanApplication · Fortinet
CVE-2016-4966
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 · uneditedThe diagnosis_control.php page in Fortinet FortiWan (formerly AscernLink) before 4.2.5 allows remote authenticated users to download PCAP files via vectors related to the UserName GET parameter.
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 confidenceFortiWan diagnosis_control.php allows authenticated remote users to download arbitrary PCAP files via the UserName GET parameter, likely due to path traversal or insufficient input validation, exposing sensitive network capture data.
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
FortiwanApplication
<= 4.2.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Identify FortiWan versionLocate the installed FortiWan version through the administrative web interface, CLI, or system information page. Compare the version number against the affected range (4.2.4 and earlier).Affected if The installed version is 4.2.4 or lower.
-
Confirm diagnosis_control.php existsCheck if the file diagnosis_control.php exists in the web directory of the FortiWan installation. This is typically found in the /diags or similar diagnostic path on the web interface.Affected if The file exists and is accessible via the web interface.
-
Test UserName parameter for path traversalWith authenticated access, attempt a GET request to diagnosis_control.php using the UserName parameter with a path traversal payload (e.g., ../../../../../../etc/passwd or a known PCAP file path). Observe if arbitrary file retrieval is possible.Affected if The UserName parameter permits directory traversal and returns files outside the intended capture directory.
-
Review access logs for suspicious PCAP downloadsExamine FortiWan web server or proxy logs for unusual diagnosis_control.php requests that include the UserName parameter, especially those accessing paths outside expected PCAP directories.Affected if Logs show PCAP download attempts using path traversal patterns.
You are affected if your FortiWan version is 4.2.4 or earlier AND the diagnosis_control.php script is accessible with the UserName parameter allowing arbitrary file retrieval via path traversal.
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.
From vendor dataUpgrade to FortiWan 4.2.5 or later to obtain the vendor patch. If immediate upgrade is not feasible, restrict access to diagnosis_control.php to trusted administrative IPs via firewall or WAF rules and monitor for anomalous PCAP download activity.
Fix this in Fortiwan
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4966 — 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-2016-4966 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