CVE-2016-5367
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 · uneditedHuawei Honor WS851 routers with software 1.1.21.1 and earlier allow remote attackers to obtain sensitive information via unspecified vectors, aka HWPSIRT-2016-05053.
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 confidenceThe Huawei Honor WS851 router with firmware 1.1.21.1 and earlier contains an information disclosure vulnerability allowing remote attackers to obtain sensitive information through unspecified vectors. The CVSS 7.5 score indicates high exploitability with network-level access, suggesting the flaw likely involves improper access controls or exposed management interfaces leaking credentials, configuration data, or session information.
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<= 1.1.21.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Identify the device modelAccess the router admin interface or check the device label to confirm the exact model is Huawei Honor WS851Affected if The device is not a Huawei Honor WS851 router, then it is not affected by this specific CVE
-
Determine the firmware versionLog into the router web interface (typically at 192.168.1.1) and navigate to System Settings or Status to find the firmware version. Alternatively, check the Huawei support site or the device label for firmware version information.Affected if The installed firmware version is 1.1.21.1 or earlier, indicating the device is vulnerable
-
Check if remote management interface is exposedAttempt to access the router web interface from an external network (WAN side) or review port forwarding/firewall rules to determine if ports 80, 443, or the management interface are accessible from the internetAffected if Remote management or the admin web interface is accessible from the WAN, increasing exposure to this information disclosure flaw
-
Review network exposureUse external port scanning tools (such as Nmap) from outside your network to check if common management ports (HTTP/HTTPS) are open and reachable on the router's public IP addressAffected if Management ports are open to the internet, indicating the device may be exploitable via network-level attack vectors
A user is affected if they have a Huawei Honor WS851 router running firmware version 1.1.21.1 or earlier with its management interface potentially exposed to network-level access.
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 dataApply any available firmware update from Huawei for the WS851 router. If no patch exists, consider network segmentation to isolate the device, disable remote management interfaces, or replace the device with a supported model.
- Consultation3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5367 — 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-5367 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