FortiwanApplication · Fortinet
CVE-2016-4967
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 · uneditedFortinet FortiWan (formerly AscernLink) before 4.2.5 allows remote authenticated users to obtain sensitive information from (1) a backup of the device configuration via script/cfg_show.php or (2) PCAP files via script/system/tcpdump.php.
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 before 4.2.5 contains an information disclosure vulnerability where authenticated users can access sensitive data through two unauthenticated PHP script endpoints: cfg_show.php exposes configuration backup files, and tcpdump.php exposes PCAP packet capture files.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check FortiWan versionLog into the FortiWan web interface or CLI and navigate to System > Status or run 'get system status' command to view the firmware versionAffected if Version is 4.2.4 or lower
-
Identify web root directoryLocate the web document root directory on the FortiWan appliance, typically /var/www/html or /htdocsAffected if Web root contains cfg_show.php and tcpdump.php files
-
Verify vulnerable PHP scripts existCheck for the presence of cfg_show.php and tcpdump.php in the web directory using file system access or directory listingAffected if Both cfg_show.php and tcpdump.php files exist in the web root
-
Test endpoint accessibilityAttempt to access http://[fortiwan-host]/cfg_show.php and http://[fortiwan-host]/tcpdump.php without authenticationAffected if Endpoints are accessible without authentication and return configuration backup or PCAP file content
-
Review access logsExamine web server access logs for requests to cfg_show.php and tcpdump.php endpoints, particularly from unauthorized IP addresses or unauthenticated sessionsAffected if Logs show access to these endpoints from users who should not have access to configuration backups or packet captures
User is affected if FortiWan version is 4.2.4 or earlier AND the cfg_show.php or tcpdump.php endpoints are accessible, allowing unauthorized access to sensitive configuration or packet capture data.
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 FortiWan to version 4.2.5 or later. Until then, restrict access to these PHP scripts and monitor for unauthorized access to configuration backups and PCAP files.
Fix this in Fortiwan
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4967 — 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-4967 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