# CVE-2016-2404: Privilege escalation in S5700, S6700, S7700, S9700,S12700,ACU2,, S5700, S6700, S7700, S9700 V200R001C00SPC300, V200R002C00SPC100, V200R003C00SPC300, V200R005C00SPC500, V200R006C00,,S12700 V200R005C00SPC500, V200R006C00,,ACU2 V200R005C00SPC500, V200R006C00,

> Improper permission control in Huawei switches allows AAA users to gain VTY access and escalate privileges when configured with AAA.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-65qg-pq7p-5fvp

## What is CVE-2016-2404?

CVE-2016-2404 is a high-severity vulnerability in S5700, S6700, S7700, S9700,S12700,ACU2,, S5700, S6700, S7700, S9700 V200R001C00SPC300, V200R002C00SPC100, V200R003C00SPC300, V200R005C00SPC500, V200R006C00,,S12700 V200R005C00SPC500, V200R006C00,,ACU2 V200R005C00SPC500, V200R006C00,, published on 2 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-264

## Which versions are affected by CVE-2016-2404?

It affects 6 products.


Products: Huawei Acu2 Firmware, Huawei S12700 Firmware, Huawei S5700 Firmware, Huawei S6700 Firmware, Huawei S7700 Firmware, Huawei S9700 Firmware.

## How do I fix CVE-2016-2404?

No fix has been published for CVE-2016-2404 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-2404 being exploited?

There is no known exploitation of CVE-2016-2404 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2404 and fix it if it is affected.

What it is: CVE-2016-2404 is a high-severity vulnerability in S5700, S6700, S7700, S9700,S12700,ACU2,, S5700, S6700, S7700, S9700 V200R001C00SPC300, V200R002C00SPC100, V200R003C00SPC300, V200R005C00SPC500, V200R006C00,,S12700 V200R005C00SPC500, V200R006C00,,ACU2 V200R005C00SPC500, V200R006C00,, published on 2 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-2404 in the wild and no public exploit code.

Affected product: S5700, S6700, S7700, S9700,S12700,ACU2,, S5700, S6700, S7700, S9700 V200R001C00SPC300, V200R002C00SPC100, V200R003C00SPC300, V200R005C00SPC500, V200R006C00,,S12700 V200R005C00SPC500, V200R006C00,,ACU2 V200R005C00SPC500, V200R006C00,. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-2404/ (Markdown: https://insights.sbomify.com/CVE-2016-2404/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-2404
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-2404
- OSV: https://osv.dev/vulnerability/CVE-2016-2404

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-2404/
Summaries are generated and may contain mistakes; the official description above is the record.