dbcve.org
S5300ei FirmwareOperating system · Huawei

CVE-2015-8677

MEDIUM · 6.5 CVSS v3.0 Published 2016-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
Memory leak in Huawei S5300EI, S5300SI, S5310HI, and S6300EI Campus series switches with software V200R003C00 before V200R003SPH011 and V200R005C00 before V200R005SPH008; S2350EI and S5300LI Campus series switches with software V200R003C00 before V200R003SPH011, V200R005C00 before V200R005SPH008, and V200R006C00 before V200R006SPH002; S9300, S7700, and S9700 Campus series switches with software V200R003C00 before V200R003SPH011, V200R005C00 before V200R005SPH009, and V200R006C00 before V200R006SPH003; S5720HI and S5720EI Campus series switches with software V200R006C00 before V200R006SPH002; and S2300 and S3300 Campus series switches with software V100R006C05 before V100R006SPH022 allows remote authenticated users to cause a denial of service (memory consumption and device restart) by logging in and out of the (1) HTTPS or (2) SFTP server, related to SSL session information.

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 · high confidence

A memory leak in Huawei Campus series switches causes memory exhaustion when authenticated users repeatedly log in and out of HTTPS or SFTP servers. The leak is related to SSL session information not being properly released, eventually causing the device to restart due to memory consumption.

MitigationUpgrade Huawei Campus switch software to the specified patched versions (V200R003SPH011, V200R005SPH008/009, V200R006SPH002/003, or V100R006SPH022 depending on model) to resolve the SSL session memory leak.

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
S5300ei FirmwareOperating system
Affected:>= v200r003c00, < v200r003sph011>= v200r005c00, < v200r005sph008
S5300si FirmwareOperating system
Affected:>= v200r001c00, < v200r001sph018>= v200r002c00, < v200r003sph011
S5310hi FirmwareOperating system
Affected:>= v200r001c00, < v200r001sph018>= v200r002c00, < v200r003sph011
S6300ei FirmwareOperating system
Affected:>= v200r001c00, < v200r001sph018>= v200r002c00, < v200r003sph011
S5300li FirmwareOperating system
Affected:>= v200r003c00, < v200r003sph011>= v200r005c00, < v200r005sph008>= v200r006c00, < v200r006sph002
S2350ei FirmwareOperating system
Affected:>= v200r003c00, < v200r003sph011>= v200r005c00, < v200r005sph008>= v200r006c00, < v200r006sph002
S9300 FirmwareOperating system
Affected:>= v200r003c00, < v200r003sph011>= v200r005c00, < v200r005sph009>= v200r006c00, < v200r006sph003
S9700 FirmwareOperating system
Affected:>= v200r003c00, < v200r003sph011>= v200r005c00, < v200r005sph009>= v200r006c00, < v200r006sph003

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

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 the switch model
    Run `display device` or check the device label to confirm the model is one of: S5300ei, S5300si, S5310hi, S6300ei, S5300li, S2350ei, S9300, or S9700
    Affected if The model is NOT one of the affected series listed in the CVE
  2. Check the firmware version
    Run `display version` to obtain the installed software version
    Affected if The version falls within any of the affected ranges: >= V200R003C00 and < V200R003SPH011; >= V200R005C00 and < V200R005SPH008/009; >= V200R006C00 and < V200R006SPH002/003; or any version < V200R001SPH018 for the early branches
  3. Verify if HTTPS server is enabled
    Run `display http server` or `display ip https server` to check if the HTTPS service is active
    Affected if HTTPS server status shows as enabled
  4. Verify if SFTP server is enabled
    Run `display ssh server status` or `display sftp server` to check if SFTP service is active
    Affected if SFTP server status shows as enabled
  5. Monitor memory usage for leak symptoms
    Run `display memory-usage` repeatedly over time while users log in and out of HTTPS or SFTP to observe if memory consumption steadily increases without recovering
    Affected if Memory usage shows continuous growth and does not return to baseline after repeated HTTPS or SFTP sessions

The device is affected if it matches an affected model, runs a firmware version within the vulnerable ranges, and has HTTPS or SFTP services enabled, with memory exhibiting abnormal growth during user login/logout cycles.

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

Upgrade Huawei Campus switch software to the specified patched versions (V200R003SPH011, V200R005SPH008/009, V200R006SPH002/003, or V100R006SPH022 depending on model) to resolve the SSL session memory leak.

Fix this in S5300ei Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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