dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-17217

MEDIUM · 5.9 CVSS v3.0 Published 2018-03-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The MGCP (Media Gateway Control Protocol) implementation in multiple Huawei video conferencing products contains an out-of-bounds write vulnerability due to insufficient validation of malformed packets. An unauthenticated remote attacker can send specially crafted MGCP packets to trigger the vulnerability, potentially causing a denial of service by impacting product availability.

MitigationApply Huawei vendor patches for the affected firmware versions. As an interim control, restrict MGCP port traffic to trusted sources using network ACLs or firewalls to reduce exposure to unauthenticated remote attackers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dp300 FirmwareOperating system
Affected:= v500r002c00
Rp200 FirmwareOperating system
Affected:= v500r002c00spc200= v600r006c00
Te30 FirmwareOperating system
Affected:= v100r001c10= v500r002c00= v600r006c00
Te40 FirmwareOperating system
Affected:= v500r002c00= v600r006c00
Te50 FirmwareOperating system
Affected:= v500r002c00= v600r006c00
Te60 FirmwareOperating system
Affected:= v100r001c10= v500r002c00= v600r006c00

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Huawei video conferencing product model
    Locate the physical device label or access the product's web interface or command-line interface to confirm the exact model (Dp300, Rp200, Te30, Te40, Te50, or Te60)
    Affected if The model is one of the affected products listed in the CVE (Dp300, Rp200, Te30, Te40, Te50, Te60)
  2. Check the installed firmware version
    Access the device via SSH or console and run the command to display the firmware version (typically 'display version' or check via the web administration interface under System Information or Device Status)
    Affected if The firmware version matches one of the affected versions: v500r002c00, v500r002c00spc200, v600r006c00, or v100r001c10 for the identified model
  3. Verify if MGCP protocol is enabled
    Access the device's web interface or CLI and check the MGCP configuration settings. In the CLI, this may be found under 'mgcp' or 'protocol mgcp' settings. Look for MGCP gateway or proxy configuration status
    Affected if MGCP protocol is enabled or configured on the device - the vulnerability only affects systems where MGCP is active
  4. Confirm network exposure of MGCP ports
    Check firewall or network ACL configurations to determine if UDP/TCP ports 2727 (MGCP signals) or other MGCP ports are accessible from untrusted networks. Use 'display current-configuration' or check the device's port exposure settings
    Affected if MGCP ports (typically 2727 and related ports) are exposed to untrusted or internet-facing networks, allowing unauthenticated attackers to send malformed packets

The environment is affected if the product model and firmware version match those listed in the CVE AND MGCP protocol is enabled AND the MGCP ports are accessible to untrusted network sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Huawei vendor patches for the affected firmware versions. As an interim control, restrict MGCP port traffic to trusted sources using network ACLs or firewalls to reduce exposure to unauthenticated remote attackers.

Fix this in Dp300 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-17217 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-17217 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data