cve.bz

CVE-2020-1815 huawei

7.5 highEPSS 0.7%

High (7.5) in huawei. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
Huawei NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00; Secospace USG6600 and USG9500 versions V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, and V500R005C00 have a memory leak vulnerability. The software does not sufficiently track and release allocated memory while parse certain message, the attacker sends the message continuously that could consume remaining memory. Successful exploit could cause memory exhaust.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-401 Missing Release of Memory after Effective Lifetime
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-2020-1815 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-1815?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-1815?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-2020-1815 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:nip6800_firmwarev500r001c30
huawei:nip6800_firmwarev500r001c60spc500
huawei:nip6800_firmwarev500r005c00
huawei:secospace_usg6600_firmwarev500r001c30spc200
huawei:secospace_usg6600_firmwarev500r001c30spc600
huawei:secospace_usg6600_firmwarev500r001c60spc500
huawei:secospace_usg6600_firmwarev500r005c00
huawei:usg9500_firmwarev500r001c30spc200
huawei:usg9500_firmwarev500r001c30spc600
huawei:usg9500_firmwarev500r001c60spc500
huawei:usg9500_firmwarev500r005c00

References

Check your stackJSON