Memory leak in Huawei S5300EI, S5300SI, S5310HI, S6300EI/ S2350EI, and S5300LI Campus series switches with software V200R001C00 before V200R
Memory leak in Huawei S5300EI, S5300SI, S5310HI, S6300EI/ S2350EI, and S5300LI Campus series switches with software V200R001C00 before V200R001SPH018, V200R002C00 before V200R003SPH011, and V200R003C00 before V200R003SPH011; S9300, S7700, and S9700 Campus series switches with software V200R001C00 before V200R001SPH023, V200R002C00 before V200R003SPH011, and V200R003C00 before V200R003SPH011; and S2300 and S3300 Campus series switches with software V100R006C05 before V100R006SPH022 allows remote attackers to cause a denial of service (memory consumption and reboot) via a large number of ICMPv6 packets.
- Published
- Apr 14, 2016
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 70th percentile
- CWE
- CWE-119
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.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| huawei | s2350ei firmware | cpe:2.3:o:huawei:s2350ei_firmware |
| huawei | s2350ei | cpe:2.3:h:huawei:s2350ei |
| huawei | s5300ei firmware | cpe:2.3:o:huawei:s5300ei_firmware |
| huawei | s5300ei | cpe:2.3:h:huawei:s5300ei |
| huawei | s5300si firmware | cpe:2.3:o:huawei:s5300si_firmware |
| huawei | s5300si | cpe:2.3:h:huawei:s5300si |
| huawei | s5310hi firmware | cpe:2.3:o:huawei:s5310hi_firmware |
| huawei | s5310hi | cpe:2.3:h:huawei:s5310hi |
| huawei | s6300ei firmware | cpe:2.3:o:huawei:s6300ei_firmware |
| huawei | s6300ei | cpe:2.3:h:huawei:s6300ei |
| huawei | s5300li firmware | cpe:2.3:o:huawei:s5300li_firmware |
| huawei | s5300li | cpe:2.3:h:huawei:s5300li |
and 10 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei s2300 firmwarev100r006c05 and later · before v100r006sph022
- huawei s2350ei firmwarev200r002c00 and later · before v200r003sph011
- huawei s2350ei firmwarev200r001c00 and later · before v200r001sph018
- huawei s3300 firmwarev100r006c05 and later · before v100r006sph022
- huawei s5300ei firmwarev200r001c00 and later · before v200r001sph018
- huawei s5300ei firmwarev200r002c00 and later · before v200r003sph011
- huawei s5300li firmwarev200r002c00 and later · before v200r003sph011
- huawei s5300li firmwarev200r001c00 and later · before v200r001sph018
- huawei s5300si firmwarev200r001c00 and later · before v200r001sph018
- huawei s5300si firmwarev200r002c00 and later · before v200r003sph011
- huawei s5310hi firmwarev200r001c00 and later · before v200r001sph018
- huawei s5310hi firmwarev200r002c00 and later · before v200r003sph011
- huawei s6300ei firmwarev200r002c00 and later · before v200r003sph011
- huawei s6300ei firmwarev200r001c00 and later · before v200r001sph018
- huawei s7700 firmwarev200r001c00 and later · before v200r001sph023
- huawei s7700 firmwarev200r002c00 and later · before v200r003c00
- huawei s7700 firmwarev200r003c00
- huawei s9300 firmwarev200r002c00 and later · before v200r003c00
- huawei s9300 firmwarev200r001c00 and later · before v200r001sph023
- huawei s9300 firmwarev200r003c00
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-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS 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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
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.