Huawei S9300 with software before V100R006SPH013 and S2300,S3300,S5300,S6300 with software before V100R006SPH010 support Y.1731 and therefor
Huawei S9300 with software before V100R006SPH013 and S2300,S3300,S5300,S6300 with software before V100R006SPH010 support Y.1731 and therefore have the Y.1731 vulnerability in processing special packets. The vulnerability causes the restart of switches.
- Published
- Apr 2, 2017
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 62th percentile
- CWE
- CWE-19
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 · 1.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| huawei | s9300 firmware | cpe:2.3:o:huawei:s9300_firmware |
| huawei | s9300 | cpe:2.3:h:huawei:s9300 |
| huawei | s3300 firmware | cpe:2.3:o:huawei:s3300_firmware |
| huawei | s3300 | cpe:2.3:h:huawei:s3300 |
| huawei | s2300 firmware | cpe:2.3:o:huawei:s2300_firmware |
| huawei | s2300 | cpe:2.3:h:huawei:s2300 |
| huawei | s5300 firmware | cpe:2.3:o:huawei:s5300_firmware |
| huawei | s5300 | cpe:2.3:h:huawei:s5300 |
| huawei | s6300 firmware | cpe:2.3:o:huawei:s6300_firmware |
| huawei | s6300 | cpe:2.3:h:huawei:s6300 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei s2300 firmwarev100r006c00spc800
- huawei s2300 firmwarev100r006c01spc100
- huawei s2300 firmwarev100r006c03
- huawei s3300 firmwarev100r006c00spc800
- huawei s3300 firmwarev100r006c01spc100
- huawei s3300 firmwarev100r006c03
- huawei s5300 firmwarev100r006c00spc800
- huawei s5300 firmwarev100r006c01spc100
- huawei s5300 firmwarev100r006c03
- huawei s6300 firmwarev100r006c00spc800
- huawei s6300 firmwarev100r006c01spc100
- huawei s6300 firmwarev100r006c03
- huawei s9300 firmwarev100r006c00spc500
- huawei s9300 firmwarev100r006c00spc800
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 S9300,S2300,S3300,S5300,S6300 S9300 with software V100R006C00SPC500??S9300 with software V100R006C00SPC800,S2300,S3300,S5300,S6300 with software V100R006C00SPC800,V100R006C01SPC100, V100R006C03
- S9300,S2300,S3300,S5300,S6300 S9300 with software V100R006C00SPC500??S9300 with software V100R006C00SPC800,S2300,S3300,S5300,S6300 with software V100R006C00SPC800,V100R006C01SPC100, V100R006C03affected
Same product
huawei: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-4705Multiple heap-based buffer overflows in the eSap software platform in Huawei Campus S9300, S7700, S9700, S5300, S5700, S6300, and S6700 seri30Monitor
- CVE-2014-5394Multiple Huawei Campus switches allow remote attackers to enumerate usernames via vectors involving use of SSH by the maintenance terminal.24Monitor
- CVE-2014-8570Huawei S9300, S9303, S9306, S9312 with software V100R002; S7700, S7703, S7706, S7712 with software V100R003, V100R006, V200R001, V200R002, V21Monitor
- CVE-2015-8085Huawei AR routers with software before V200R007C00SPC100; Quidway S9300 routers with software before V200R009C00; S12700 routers with softwa19Monitor
- CVE-2015-7846Huawei S7700, S9700, S9300 before V200R07C00SPC500, and AR200, AR1200, AR2200, AR3200 before V200R005C20SPC200 allows attackers with physica18Monitor
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.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-19 · Data Processing ErrorsCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.