Huawei switches S5700, S6700, S7700, S9700 with software V200R001C00SPC300, V200R002C00SPC100, V200R003C00SPC300, V200R005C00SPC500, V200R00
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.
- Published
- Apr 2, 2017
- Updated
- Jun 16, 2026
- EPSS
- 0.8% · 54th percentile
- CWE
- CWE-264
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| huawei | s5700 firmware | cpe:2.3:o:huawei:s5700_firmware |
| huawei | s5700 | cpe:2.3:h:huawei:s5700 |
| huawei | s6700 firmware | cpe:2.3:o:huawei:s6700_firmware |
| huawei | s6700 | cpe:2.3:h:huawei:s6700 |
| huawei | s7700 firmware | cpe:2.3:o:huawei:s7700_firmware |
| huawei | s7700 | cpe:2.3:h:huawei:s7700 |
| huawei | s9700 firmware | cpe:2.3:o:huawei:s9700_firmware |
| huawei | s9700 | cpe:2.3:h:huawei:s9700 |
| huawei | s12700 firmware | cpe:2.3:o:huawei:s12700_firmware |
| huawei | s12700 | cpe:2.3:h:huawei:s12700 |
| huawei | acu2 firmware | cpe:2.3:o:huawei:acu2_firmware |
| huawei | acu2 | cpe:2.3:h:huawei:acu2 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei acu2 firmwarev200r005c00spc500
- huawei acu2 firmwarev200r006c00
- huawei s12700 firmwarev200r005c00spc500
- huawei s12700 firmwarev200r006c00
- huawei s5700 firmwarev200r001c00spc300
- huawei s5700 firmwarev200r002c00spc100
- huawei s5700 firmwarev200r003c00spc300
- huawei s5700 firmwarev200r005c00spc500
- huawei s5700 firmwarev200r006c00
- huawei s6700 firmwarev200r001c00spc300
- huawei s6700 firmwarev200r002c00spc100
- huawei s6700 firmwarev200r003c00spc300
- huawei s6700 firmwarev200r005c00spc500
- huawei s6700 firmwarev200r006c00
- huawei s7700 firmwarev200r001c00spc300
- huawei s7700 firmwarev200r002c00spc100
- huawei s7700 firmwarev200r003c00spc300
- huawei s7700 firmwarev200r005c00spc500
- huawei s7700 firmwarev200r006c00
- huawei s9700 firmwarev200r001c00spc300
Versions reported by the vendor
Affected version ranges reported by the assigning authority (huawei). Independent of NVD's CPE analysis and usually ahead of it.
n/a S5700, S6700, S7700, S9700,S12700,ACU2,, S5700, S6700, S7700, S9700 V200R001C00SPC300, V200R002C00SPC100, V200R003C00SPC300, V200R005C00SPC500, V200R006C00,,S12700 V200R005C00SPC500, V200R006C00,,ACU2
- S5700, S6700, S7700, S9700,S12700,ACU2,, S5700, S6700, S7700, S9700 V200R001C00SPC300, V200R002C00SPC100, V200R003C00SPC300, V200R005C00SPC500, V200R006C00,,S12700 V200R005C00SPC500, V200R006C00,,ACU2affected
Same product
huawei: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-2800The user authentication module in Huawei Campus switches S5700, S5300, S6300, and S6700 with software before V200R001SPH012 and S7700, S930031Monitor
- CVE-2021-22359There is a denial of service vulnerability in the verisions V200R005C00SPC500 of S5700 and V200R005C00SPC500 of S6700.30Monitor
- CVE-2017-15324Huawei S5700 and S6700 with software of V200R005C00 have a DoS vulnerability due to insufficient validation of the Network Quality Analysis 30Monitor
- CVE-2019-5290Huawei S5700 and S6700 have a DoS security vulnerability.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.