dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-17284

MEDIUM · 5.3 CVSS v3.0 Published 2018-02-15
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 V100R001C01, V100R001C10, V500R002C00, V600R006C00 have a resource management error vulnerability. A remote attacker may send huge number of specially crafted SIP messages to the affected products. Due to improper handling of some value in the messages, successful exploit will cause 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 · moderate confidence

This is a denial-of-service vulnerability in Huawei video conferencing endpoints (DP300, RP200, TE30-TE60). A remote attacker can send large volumes of specially crafted SIP messages with certain malformed values. The affected devices improperly handle these SIP message values, exhausting resources and causing services to become abnormal/unavailable.

MitigationApply vendor-provided firmware patches when available. As an interim control, implement SIP traffic rate limiting or SIP ALG filtering at the network edge to block malformed SIP messages before they reach affected devices.

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:= v100r001c01= 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 CLI and retrieve the hardware model identifier (such as DP300, RP200, TE30, TE40, TE50, or TE60)
    Affected if The device model is one of: DP300, RP200, TE30, TE40, TE50, or TE60
  2. Retrieve the installed firmware version
    Access the device CLI or web interface and run the command to display the firmware version (commonly 'display version' or found in system information)
    Affected if The firmware version matches any of these: v500r002c00, v600r006c00, v100r001c10, or v100r001c01 for the identified model
  3. Confirm SIP service is enabled
    Check the device configuration for SIP protocol settings, typically found under VoIP, telephony, or SIP configuration menus
    Affected if SIP is enabled and the device is accepting SIP signaling traffic on the network
  4. Verify SIP message handling behavior
    Monitor device resource usage (CPU, memory) while processing SIP traffic or review SIP-related logs for abnormal message processing patterns
    Affected if Device shows signs of resource exhaustion or abnormal behavior when processing SIP messages, or logs indicate malformed SIP message processing issues

A user is affected if they have a Huawei DP300, RP200, TE30, TE40, TE50, or TE60 device running one of the specified firmware versions with SIP service enabled and processing SIP traffic on the network.

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 vendor-provided firmware patches when available. As an interim control, implement SIP traffic rate limiting or SIP ALG filtering at the network edge to block malformed SIP messages before they reach affected devices.

Fix this in Dp300 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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