dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-15336

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
The SIP backup feature in Huawei DP300 V500R002C00, IPS Module V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, NGFW Module V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R002C00, V500R002C10, NIP6300 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6600 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6800 V500R001C50, RP200 V500R002C00, V600R006C00, SVN5600 V200R003C00, V200R003C10, SVN5800 V200R003C00, V200R003C10, SVN5800-C V200R003C00, V200R003C10, SeMG9811 V300R001C01, Secospace USG6300 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6500 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6600 V100R001C00, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, TE30 V100R001C02, V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00, USG9500 V500R001C00, V500R001C20, V500R001C30, USG9520 V300R001C01, V300R001C20, USG9560 V300R001C01, V300R001C20, USG9580 V300R001C01, V300R001C20, VP9660 V200R001C02, V200R001C30, V500R002C00, V500R002C10, ViewPoint 8660 V100R008C03, ViewPoint 9030 V100R011C02, V100R011C03, eSpace U1981 V100R001C20, V200R003C00, V200R003C20, V200R003C30 has a buffer overflow vulnerability. An attacker may send specially crafted messages to the affected products. Due to the insufficient validation of some values for SIP messages, successful exploit may cause 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 · high confidence

Buffer overflow vulnerability in the SIP backup feature of multiple Huawei products. The vulnerability stems from insufficient validation of certain values within SIP messages, allowing an attacker to send specially crafted messages that can cause service abnormalities (likely denial of service).

MitigationApply vendor-supplied patches for affected products; if patches are unavailable, restrict access to SIP services/ports from untrusted networks and monitor for anomalous 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
Ips Module FirmwareOperating system
Affected:= v100r001c10= v100r001c20= v100r001c30= v500r001c00= v500r001c20= v500r001c30= v500r001c50
Ngfw Module FirmwareOperating system
Affected:= v100r001c10= v100r001c20= v100r001c30= v500r001c00= v500r001c20= v500r002c00= v500r002c10
Nip6300 FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30= v500r001c50
Nip6600 FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30= v500r001c50
Nip6800 FirmwareOperating system
Affected:= v500r001c50
Rp200 FirmwareOperating system
Affected:= v500r002c00= v600r006c0
Svn5600 FirmwareOperating system
Affected:= v200r003c00= v200r003c10

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 and firmware version
    Access the device admin console or run 'display version' command via CLI to retrieve the exact model name and firmware version number
    Affected if The device model is Dp300, Ips Module, Ngfw Module, Nip6300, Nip6600, Nip6800, Rp200, or Svn5600 AND the firmware version matches exactly one of the listed vulnerable versions (e.g., v500r002c00 for Dp300, v500r001c50 for Ips Module, etc.)
  2. Determine if SIP backup feature is enabled
    Check the device configuration for SIP backup or SIP trunk settings. In the CLI, use 'display current-configuration' and search for 'sip', 'backup', or 'sip-backup' related configuration blocks
    Affected if The SIP backup feature is configured and active on the device
  3. Verify SIP service listening status
    Check if SIP ports (typically UDP/TCP 5060) are open and listening. Use 'display ip socket' or 'display firewall session' commands, or run a network port scan against the device
    Affected if The device has SIP ports open and accepting connections, especially from untrusted networks
  4. Review SIP message handling configuration
    Examine the SIP profile or SIP gateway settings in the device configuration for any inspection,ALG (Application Layer Gateway), or deep inspection settings related to SIP
    Affected if SIP ALG or SIP inspection is enabled without the vendor patch applied

The environment is affected if the device model and firmware version exactly match one of the vulnerable versions listed AND the SIP backup feature is enabled and accessible.

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 for affected products; if patches are unavailable, restrict access to SIP services/ports from untrusted networks and monitor for anomalous SIP traffic.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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