dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-17150

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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
Timergrp module in Huawei DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V500R002C00; V600R006C00; TE40 V500R002C00; V600R006C00; TE50 V500R002C00; V600R006C00; TE60 V100R001C10; V500R002C00; V600R006C00 have an DoS vulnerability due to insufficient validation of the parameter. An authenticated local attacker may call a special API with special parameter, which cause an infinite loop. Successful exploit of this vulnerability can allow an attacker to launch DOS attack.

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 Timergrp module in multiple Huawei video conferencing devices (DP300, RP200, TE30/40/50/60) contains a DoS vulnerability caused by insufficient validation of API parameters. An authenticated local attacker can call a specific API with a specially crafted parameter that triggers an infinite loop, causing the device to become unresponsive.

MitigationApply vendor-supplied firmware updates for affected versions (V500R002C00, V600R006C00, V100R001C10). Until patches are available, restrict local authenticated access to trusted personnel only and monitor for devices becoming unresponsive.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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 device model
    Determine the exact model number of the Huawei video conferencing device (DP300, RP200, TE30, TE40, TE50, or TE60)
    Affected if Device model is DP300, RP200, TE30, TE40, TE50, or TE60
  2. Check firmware version
    Retrieve the installed firmware version from the device system settings or via CLI command such as 'display version' or 'system-info'
    Affected if Firmware version matches v100r001c10, v500r002c00, or v600r006c00 for the affected model
  3. Verify Timergrp module presence
    Check if the Timergrp module is loaded or available on the device, typically via 'display module' or similar system information command
    Affected if Timergrp module is present and accessible on the device
  4. Confirm API access capability
    Verify whether authenticated local access to the device API interface is available, typically through CLI or web management portal
    Affected if Authenticated local API access is enabled and reachable
  5. Check for device responsiveness
    Ping the device or attempt to access the management interface to verify normal operation
    Affected if Device is unresponsive or experiencing denial of service symptoms

A user is affected if the device is a Huawei DP300, RP200, TE30, TE40, TE50, or TE60 running firmware version v100r001c10, v500r002c00, or v600r006c00, the Timergrp module is present, and the device has become unresponsive due to an infinite loop triggered by a specially crafted API parameter.

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-supplied firmware updates for affected versions (V500R002C00, V600R006C00, V100R001C10). Until patches are available, restrict local authenticated access to trusted personnel only and monitor for devices becoming unresponsive.

Fix this in Dp300 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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