dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-17316

MEDIUM · 5.3 CVSS v3.0 Published 2018-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
Huawei DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V500R002C00; V600R006C00; TE40 V500R002C00; V600R006C00; TE50 V500R002C00; V600R006C00; TE60 V100R001C10; V500R002C00; V600R006C00 have an out-of-bounds read vulnerability. An unauthenticated, remote attacker has to control the peer device and craft the Signalling Connection Control Part (SCCP) messages to the target devices. Due to insufficient input validation of some values in the messages, successful exploit will cause out-of-bounds read and some services abnormal.

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 · high confidence

Multiple Huawei video conferencing devices (DP300, RP200, TE30, TE40, TE50, TE60) contain an out-of-bounds read vulnerability in their SCCP (Signalling Connection Control Part) message handling. An unauthenticated, remote attacker controlling the peer device can send specially crafted SCCP messages with insufficiently validated values, causing the device to read memory outside allocated buffers and resulting in service abnormalities.

MitigationApply the vendor-supplied firmware updates for affected devices. As an interim control, restrict network access to these devices and implement firewall rules to limit SCCP traffic to trusted endpoints.

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:= v500r002c00= 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

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

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 device model
    Access the device management interface or check the device label/serial number to confirm the model is one of: DP300, RP200, TE30, TE40, TE50, or TE60
    Affected if The device model is DP300, RP200, TE30, TE40, TE50, or TE60
  2. Determine the installed firmware version
    Log into the device administration panel or use the command line interface (typically via SSH/Telnet) and execute the command to display firmware version, such as 'display version' or check under system information settings
    Affected if The firmware version matches any of these: v500r002c00, v600r006c00, or v100r001c10
  3. Verify if SCCP is enabled
    Access the device configuration settings and check the SCCP (Signalling Connection Control Part) protocol configuration. This is typically found under VoIP/SIP settings or telecommunications protocol settings in the device web interface or CLI using 'display current-configuration' to search for SCCP-related entries
    Affected if SCCP protocol is enabled or configured on the device (the vulnerability only triggers when SCCP is active and processing messages from a remote peer)
  4. Assess network exposure to untrusted peers
    Review firewall rules and network access control lists (ACLs) protecting the device. Check if the device SCCP port (default port 2000 for SCCP) is accessible from untrusted network segments or the public internet
    Affected if The device SCCP service is reachable from untrusted network sources without proper filtering

The device is affected if it is a DP300, RP200, TE30, TE40, TE50, or TE60 running firmware version v500r002c00, v600r006c00, or v100r001c10 AND has SCCP enabled AND is accessible to untrusted remote attackers who can send crafted SCCP messages.

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 the vendor-supplied firmware updates for affected devices. As an interim control, restrict network access to these devices and implement firewall rules to limit SCCP traffic to trusted endpoints.

Fix this in Dp300 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-17316 — 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-17316 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