cve.bz

CVE-2015-8677 huawei: Resource Management Errors

6.5 mediumEPSS 1.1%

Medium (6.5) in huawei. EPSS 1.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.0

6.5 medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 67th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-399 Resource Management Errors
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2015-8677 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2015-8677?via=ask-ai-copy and https://cve.bz/cve/CVE-2015-8677?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2015-8677 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:s5300ei_firmwarefrom v200r003c00 before v200r003sph011
huawei:s5300ei_firmwarefrom v200r005c00 before v200r005sph008
huawei:s5300si_firmwarefrom v200r001c00 before v200r001sph018
huawei:s5300si_firmwarefrom v200r002c00 before v200r003sph011
huawei:s5310hi_firmwarefrom v200r001c00 before v200r001sph018
huawei:s5310hi_firmwarefrom v200r002c00 before v200r003sph011
huawei:s6300ei_firmwarefrom v200r001c00 before v200r001sph018
huawei:s6300ei_firmwarefrom v200r002c00 before v200r003sph011
huawei:s5300li_firmwarefrom v200r003c00 before v200r003sph011
huawei:s5300li_firmwarefrom v200r005c00 before v200r005sph008
huawei:s5300li_firmwarefrom v200r006c00 before v200r006sph002
huawei:s2350ei_firmwarefrom v200r003c00 before v200r003sph011
huawei:s2350ei_firmwarefrom v200r005c00 before v200r005sph008
huawei:s2350ei_firmwarefrom v200r006c00 before v200r006sph002
huawei:s9300_firmwarefrom v200r003c00 before v200r003sph011
huawei:s9300_firmwarefrom v200r005c00 before v200r005sph009
huawei:s9300_firmwarefrom v200r006c00 before v200r006sph003
huawei:s9700_firmwarefrom v200r003c00 before v200r003sph011
huawei:s9700_firmwarefrom v200r005c00 before v200r005sph009
huawei:s9700_firmwarefrom v200r006c00 before v200r006sph003
huawei:s7700_firmwarefrom v200r003c00 before v200r003sph011
huawei:s7700_firmwarefrom v200r005c00 before v200r005sph009
huawei:s7700_firmwarefrom v200r006c00 before v200r006sph003
huawei:s5720hi_firmwarefrom v200r006c00 before v200r006sph002
huawei:s5720ei_firmwarefrom v200r006c00 before v200r006sph002
huawei:s2300_firmwarefrom v100r006c05 before v100r006sph022
huawei:s3300_firmwarefrom v100r006c05 before v100r006sph022

References

Check your stackJSON