dbcve.org
S5700 FirmwareOperating system · Huawei

CVE-2016-2404

HIGH · 7.5 CVSS v3.0 Published 2017-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
Huawei switches S5700, S6700, S7700, S9700 with software V200R001C00SPC300, V200R002C00SPC100, V200R003C00SPC300, V200R005C00SPC500, V200R006C00; S12700 with software V200R005C00SPC500, V200R006C00; ACU2 with software V200R005C00SPC500, V200R006C00 have a permission control vulnerability. If a switch enables Authentication, Authorization, and Accounting (AAA) for permission control and user permissions are not appropriate, AAA users may obtain the virtual type terminal (VTY) access permission, resulting in privilege escalation.

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

This privilege escalation vulnerability affects Huawei switches (S5700, S6700, S7700, S9700, S12700, ACU2) when AAA is enabled for permission control. If user permissions are improperly configured, authenticated AAA users can obtain VTY (Virtual Type Terminal) access permission, allowing them to escalate from their assigned privilege level to higher system privileges.

MitigationReview and properly configure AAA user permission settings, ensuring VTY access is restricted according to the principle of least privilege. Verify that AAA users are assigned only the minimum permissions required for their legitimate roles.

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
S5700 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300= v200r005c00spc500= v200r006c00
S6700 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300= v200r005c00spc500= v200r006c00
S7700 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300= v200r005c00spc500= v200r006c00
S9700 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300= v200r005c00spc500= v200r006c00
S12700 FirmwareOperating system
Affected:= v200r005c00spc500= v200r006c00
Acu2 FirmwareOperating system
Affected:= v200r005c00spc500= v200r006c00

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

CVSS:3.0/AV:N/AC:H/PR:L/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 device model
    Run the display device or display version command to confirm the switch model is S5700, S6700, S7700, S9700, S12700, or ACU2
    Affected if The device is one of the listed affected models
  2. Check firmware version
    Run the display version command to obtain the installed firmware version, then compare it against the affected version ranges: v200r001c00spc300, v200r002c00spc100, v200r003c00spc300, v200r005c00spc500, v200r006c00
    Affected if The firmware version matches one of the affected versions listed for your model
  3. Verify AAA is enabled
    Run the display current-configuration | include aaa command or display aaa configuration to check if AAA is configured and enabled on the device
    Affected if AAA is enabled and being used for authentication or authorization
  4. Confirm AAA permission control is in use
    Run display current-configuration | include user to examine AAA user configurations, and check if authentication-mode or authorization-mode is set to aaa in the VTY or user-interface views
    Affected if AAA is configured for authentication or authorization on user interfaces
  5. Check VTY line configuration and privilege assignment
    Run display current-configuration | include vty or display user-interface to view VTY line settings, then examine how AAA users are mapped to privilege levels (such as through user privilege or local user configurations)
    Affected if VTY lines exist and AAA users can obtain VTY access permission that allows privilege escalation beyond their assigned level

The environment is affected if the device is a listed model, runs an affected firmware version, has AAA enabled for permission control, and allows AAA users to access VTY lines with the ability to escalate privileges beyond their assigned level.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and properly configure AAA user permission settings, ensuring VTY access is restricted according to the principle of least privilege. Verify that AAA users are assigned only the minimum permissions required for their legitimate roles.

Fix this in S5700 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-2404 — 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-2404 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