dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-17219

MEDIUM · 5.3 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 →
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 vulnerabilities. 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 · high confidence

The SCCPX module in affected Huawei video conferencing products contains an input validation vulnerability where it fails to properly validate malformed packets with specific parameters. An unauthenticated remote attacker can send specially crafted packets to trigger invalid memory access, resulting in denial of service.

MitigationApply vendor-provided firmware updates from Huawei to patch the SCCPX module input validation vulnerability. If patches are unavailable, consider network segmentation to limit exposure to unauthenticated 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:= 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
    Log into the device management interface or check the physical device label to determine the model (Dp300, Rp200, Te30, Te40, Te50, or Te60)
    Affected if The model is NOT one of the affected products (Dp300, Rp200, Te30, Te40, Te50, Te60)
  2. Check the installed firmware version
    Access the device CLI or web management interface and run 'display version' or navigate to the system information page to retrieve the firmware version
    Affected if The firmware version matches any of the affected versions: v500r002c00, v600r006c00, v100r001c10 (depending on model)
  3. Verify the SCCPX module is active
    Check the device configuration or module status via CLI command 'display module-information sccpx' or through the web interface module status page
    Affected if The SCCPX module is loaded and active on the device
  4. Assess network exposure to unauthenticated attackers
    Review firewall rules and access control lists to determine if the SCCPX service port (typically UDP/5060 or UDP/5061 for SIP-based video conferencing) is exposed to untrusted networks
    Affected if The SCCPX service port is accessible from untrusted or public networks without authentication

A user is affected if they run one of the listed Huawei models with a matching firmware version and have the SCCPX module enabled and network-accessible to unauthenticated 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-provided firmware updates from Huawei to patch the SCCPX module input validation vulnerability. If patches are unavailable, consider network segmentation to limit exposure to unauthenticated attackers.

Fix this in Dp300 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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