dbcve.org
Honor Ws851 FirmwareOperating system · Huawei

CVE-2016-5365

CRITICAL · 9.8 CVSS v3.0 Published 2016-06-14
Fix available
A fix is available. Upgrade to after 1.1.21.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Stack-based buffer overflow in Huawei Honor WS851 routers with software 1.1.21.1 and earlier allows remote attackers to execute arbitrary commands with root privileges via unspecified vectors, aka HWPSIRT-2016-05051.

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 confidence

Stack-based buffer overflow in Huawei Honor WS851 routers with software 1.1.21.1 and earlier allows remote unauthenticated attackers to execute arbitrary commands with root privileges via unspecified vectors, achieving complete device compromise.

MitigationApply vendor firmware update when available; if no patch exists, restrict network exposure by placing device behind a firewall or disabling remote management interfaces.

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
Honor Ws851 FirmwareOperating system
Affected:<= 1.1.21.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Identify the router model
    Check the device label or web management interface to confirm the model is Huawei Honor WS851
    Affected if The device is not a Huawei Honor WS851 router
  2. Check the firmware version
    Access the router's web interface (typically at 192.168.1.1) and look for the firmware version in the system status or administration section, or check the upgrade page
    Affected if The firmware version is 1.1.21.1 or earlier
  3. Determine if remote management is accessible
    Check if the router's web interface is accessible from outside the local network by attempting to access the WAN IP on ports 80/443, or review port forwarding/firewall rules
    Affected if The router's management interface is exposed to the internet (WAN side)
  4. Verify the vulnerability trigger service
    Confirm that the router's HTTP service is running and accepting connections from the network interface in question
    Affected if The HTTP service is running and accessible on the exposed interface

A user is affected if they have a Huawei Honor WS851 router running firmware version 1.1.21.1 or earlier with the management interface exposed to the network where the attack can reach it.

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 a release after 1.1.21.1
Interim mitigation

Apply vendor firmware update when available; if no patch exists, restrict network exposure by placing device behind a firewall or disabling remote management interfaces.

Recommended fix Moderate confidence

Firmware version newer than 1.1.21.1 (check Huawei support site for latest available release)

  1. 1. Identify the current firmware version of the Honor WS851 router by accessing the router's web management interface or checking the device settings.
  2. 2. Navigate to Huawei's official support website or the Honor support page for the WS851 router.
  3. 3. Look for firmware updates in the Downloads or Support section for the WS851 model.
  4. 4. If a firmware version newer than 1.1.21.1 is available, download the latest stable firmware release.
  5. 5. Access the router's administrative interface, locate the firmware upgrade section, and upload the new firmware file.
  6. 6. After upgrading, verify the new firmware version is installed and confirm the device is functioning normally.
  7. 7. If no firmware update is available from Huawei, consider implementing network segmentation to limit the router's exposure to untrusted networks, and monitor for any official security advisories.
Caveat Standard firmware upgrade risks apply - ensure stable power during upgrade and backup configuration if possible

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

Fix this in Honor Ws851 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-5365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2016-5365 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