dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-17144

MEDIUM · 5.3 CVSS v3.0 Published 2018-03-05
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
Backup feature of SIP module in Huawei DP300 V500R002C00; V500R002C00SPC100; V500R002C00SPC200; V500R002C00SPC300; V500R002C00SPC400; V500R002C00SPC500; V500R002C00SPC600; V500R002C00SPC800; V500R002C00SPC900; V500R002C00SPCa00; RP200 V500R002C00SPC200; V600R006C00; V600R006C00SPC200; RSE6500 V500R002C00SPC100; V500R002C00SPC200; V500R002C00SPC300; V500R002C00SPC300T; V500R002C00SPC500; V500R002C00SPC600; V500R002C00SPC700; V500R002C00T; TE30 V100R001C10; V100R001C10SPC100; V100R001C10SPC200B010; V100R001C10SPC300; V100R001C10SPC500; V100R001C10SPC600; V100R001C10SPC700B010; V100R001C10SPC800; V500R002C00SPC200; V500R002C00SPC500; V500R002C00SPC600; V500R002C00SPC700; V500R002C00SPC900; V500R002C00SPCb00; V600R006C00; TE40 V500R002C00SPC600; V500R002C00SPC700; V500R002C00SPC900; V500R002C00SPCb00; V600R006C00; V600R006C00SPC200; TE50 V500R002C00SPC600; V500R002C00SPC700; V500R002C00SPCb00; V600R006C00; V600R006C00SPC200; TE60 V100R001C01SPC100; V100R001C01SPC107TB010; V100R001C10; V100R001C10SPC300; V100R001C10SPC400; V100R001C10SPC500; V100R001C10SPC600; V100R001C10SPC700; V100R001C10SPC800; V100R001C10SPC900; V500R002C00; V500R002C00SPC100; V500R002C00SPC200; V500R002C00SPC300; V500R002C00SPC600; V500R002C00SPC700; V500R002C00SPC800; V500R002C00SPC900; V500R002C00SPCa00; V500R002C00SPCb00; V500R002C00SPCd00; V600R006C00; V600R006C00SPC100; V600R006C00SPC200; V600R006C00SPC300; TP3106 V100R002C00; V100R002C00SPC200; V100R002C00SPC400; V100R002C00SPC600; V100R002C00SPC700; V100R002C00SPC800; TP3206 V100R002C00; V100R002C00SPC200; V100R002C00SPC400; V100R002C00SPC600; V100R002C00SPC700; V100R002C10; ViewPoint 9030 V100R011C02SPC100; V100R011C03B012SP15; V100R011C03B012SP16; V100R011C03B015SP03; V100R011C03LGWL01SPC100; V100R011C03SPC100; V100R011C03SPC200; V100R011C03SPC300; V100R011C03SPC400; V100R011C03SPC500; eSpace U1960 V200R003C30SPC200; eSpace U1981 V100R001C20SPC700; V200R003C20SPCa00 has an overflow vulnerability when the module process a specific amount of state. The module cannot handle it causing SIP module DoS.

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 buffer/integer overflow vulnerability exists in the backup feature of the SIP module across multiple Huawei video conferencing and unified communication devices. When the module processes a specific amount of state data, it fails to properly handle the condition, leading to a denial of service condition where the SIP module becomes unavailable.

MitigationApply vendor-supplied firmware patches to affected Huawei devices. Until patches are available, consider network segmentation to limit exposure to the SIP module and implement rate limiting on SIP traffic.

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= v500r002c00spc100= v500r002c00spc200= v500r002c00spc300= v500r002c00spc400= v500r002c00spc500= v500r002c00spc600= v500r002c00spc800= v500r002c00spc900= v500r002c00spca00
Rp200 FirmwareOperating system
Affected:= v500r002c00spc200= v600r006c00= v600r006c00spc200
Rse6500 FirmwareOperating system
Affected:= v500r002c00spc100= v500r002c00spc200= v500r002c00spc300= v500r002c00spc300t= v500r002c00spc500= v500r002c00spc600= v500r002c00spc700= v500r002c00t
Te30 FirmwareOperating system
Affected:= v100r001c10= v100r001c10spc100= v100r001c10spc200b010= v100r001c10spc300= v100r001c10spc500= v100r001c10spc600= v100r001c10spc700b010= v100r001c10spc800= v500r002c00spc200= v500r002c00spc500= v500r002c00spc600= v500r002c00spc700
Te40 FirmwareOperating system
Affected:= v500r002c00spc600= v500r002c00spc700= v500r002c00spc900= v500r002c00spcb00= v600r006c00= v600r006c00spc200
Te50 FirmwareOperating system
Affected:= v500r002c00spc600= v500r002c00spc700= v500r002c00spcb00= v600r006c00= v600r006c00spc200
Te60 FirmwareOperating system
Affected:= v100r001c01spc100= v100r001c01spc107tb010= v100r001c10= v100r001c10spc300= v100r001c10spc400= v100r001c10spc500= v100r001c10spc600= v100r001c10spc700= v100r001c10spc800= v100r001c10spc900= v500r002c00= v500r002c00spc100
Tp3106 FirmwareOperating system
Affected:= v100r002c00= v100r002c00spc200= v100r002c00spc400= v100r002c00spc600= v100r002c00spc700= v100r002c00spc800

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 use 'display device' command to confirm the exact model (Dp300, Rp200, Rse6500, Te30, Te40, Te50, Te60, or Tp3106)
    Affected if Device model is one of the listed affected products
  2. Check the installed firmware version
    Use 'display version' command or access device info page to retrieve the current firmware version string
    Affected if Installed version matches any of the exact versions listed in the affected version ranges (e.g., v500r002c00, v600r006c00, v100r001c10, etc.)
  3. Verify SIP module is enabled
    Use 'display sip status' or check SIP configuration via 'display current-configuration | include sip' to confirm the SIP module is active
    Affected if SIP module is enabled and running on the device
  4. Confirm backup feature accessibility
    Check if backup functionality for SIP is configured via 'display sip backup' or review backup-related configuration settings in the device
    Affected if SIP backup feature is configured or accessible (this is the component containing the vulnerability)

A user is affected if they are running any of the listed firmware versions on the specified Huawei devices with the SIP module enabled and the backup feature in use.

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 patches to affected Huawei devices. Until patches are available, consider network segmentation to limit exposure to the SIP module and implement rate limiting on SIP traffic.

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-17144 — 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-17144 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