dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-17308

MEDIUM · 5.3 CVSS v3.0 Published 2018-04-11
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
SCCPX module in Huawei DP300 V500R002C00, RP200 V500R002C00, V600R006C00, TE30 V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C10, V500R002C00, V600R006C00 has an invalid memory access vulnerability. An unauthenticated, remote attacker may send specially crafted packets to the affected products. Due to insufficient validation of packets, successful exploit may 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

A memory access vulnerability exists in the SCCPX module of multiple Huawei video conferencing products (DP300, RP200, TE30/40/50/60). The issue stems from insufficient validation of incoming network packets, allowing unauthenticated remote attackers to send specially crafted packets that trigger invalid memory access, potentially causing service disruption.

MitigationApply vendor-supplied patches or firmware updates for the affected product versions. If patches are unavailable, restrict network access to the SCCPX module via firewall rules or network segmentation to limit exposure to untrusted sources.

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:= v500r002c00spcb00
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 Huawei video conferencing product model
    Locate the physical device label or access the device's web interface or admin console to confirm the model number (DP300, RP200, TE30, TE40, TE50, or TE60)
    Affected if The model is one of DP300, RP200, TE30, TE40, TE50, or TE60 and falls within the affected version range
  2. Check the installed firmware version
    Access the device admin interface or use the command line interface (CLI) to retrieve the firmware version. For CLI, typically use 'display version' or check the system information page in the web interface
    Affected if The firmware version matches v500r002c00spcb00 (DP300), v500r002c00 or v600r006c00 (RP200), v100r001c10, v500r002c00, or v600r006c00 (TE30/TE40/TE50/TE60)
  3. Verify if the SCCPX module is enabled
    Access the device's configuration settings or run CLI commands such as 'display current-configuration' or 'display sccpx status' to check if the SCCPX module is active
    Affected if The SCCPX module is enabled and running on the device
  4. Check network exposure of the SCCPX service
    Review firewall rules, port listings (using 'display port' or 'display ip interface'), and network access controls to determine if the SCCPX service ports are exposed to untrusted networks
    Affected if The SCCPX service ports are accessible from untrusted or external networks without proper filtering

The environment is affected if the device is a DP300, RP200, TE30, TE40, TE50, or TE60 running one of the specific firmware versions listed AND the SCCPX module is enabled and potentially exposed to network attackers.

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 patches or firmware updates for the affected product versions. If patches are unavailable, restrict network access to the SCCPX module via firewall rules or network segmentation to limit exposure to untrusted sources.

Fix this in Dp300 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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