dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-15323

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
Huawei DP300 V500R002C00, NIP6600 V500R001C00, V500R001C20, V500R001C30, Secospace USG6500 V500R001C00, V500R001C20, V500R001C30, TE60 V100R001C01, V100R001C10, V100R003C00, V500R002C00, V600R006C00, TP3106 V100R001C06, V100R002C00, VP9660 V200R001C02, V200R001C30, V500R002C00, V500R002C10, ViewPoint 8660 V100R008C03, ViewPoint 9030 V100R011C02, V100R011C03, eCNS210_TD V100R004C10, eSpace U1981 V200R003C30 have a DoS vulnerability caused by memory exhaustion in some Huawei products. For lacking of adequate input validation, attackers can craft and send some malformed messages to the target device to exhaust the memory of the device and cause a Denial of Service (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 · high confidence

The vulnerability exists due to insufficient input validation in the message parsing functionality of affected Huawei devices (DP300, NIP6600, USG6500, TE60, TP3106, VP9660, ViewPoint, eCNS210_TD, eSpace U1981). An unauthenticated remote attacker can send specially crafted malformed messages to trigger memory exhaustion, causing the device to become unresponsive and resulting in a Denial of Service.

MitigationApply vendor-supplied firmware patches for the specific product versions listed. If patches are unavailable, implement network-level access controls and traffic filtering to reduce attack surface exposure.

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
Nip6600 FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30
Secospace Usg6500 FirmwareOperating system
Affected:= v500r001c00= v500r001c20= v500r001c30
Te60 FirmwareOperating system
Affected:= v100r001c01= v100r001c10= v100r003c00= v500r002c00= v600r006c00
Tp3106 FirmwareOperating system
Affected:= v100r001c06= v100r002c00
Vp9660 FirmwareOperating system
Affected:= v200r001c02= v200r001c30= v500r002c00= v500r002c10
Viewpoint 8660 FirmwareOperating system
Affected:= v100r008c03
Viewpoint 9030 FirmwareOperating system
Affected:= v100r011c02= v100r011c03

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 the Huawei device model
    Access the device management interface or check device documentation to determine the exact model (e.g., DP300, NIP6600, USG6500, TE60, TP3106, VP9660, ViewPoint 8660, ViewPoint 9030, eCNS210_TD, or eSpace U1981)
    Affected if The device model is any of the listed affected products: DP300, NIP6600, USG6500, TE60, TP3106, VP9660, ViewPoint 8660, ViewPoint 9030, eCNS210_TD, or eSpace U1981
  2. Check the firmware version
    Log into the device admin interface or use the command line interface (CLI) to retrieve the firmware version. Common commands include 'display version' or checking the system information page
    Affected if The installed firmware version matches exactly one of the affected versions listed for that specific model
  3. Verify message parsing service is network-accessible
    Check the device network configuration to determine if the message parsing functionality (typically via SIP, H.323, or similar protocols for these devices) is exposed to external network interfaces or the internet
    Affected if The message parsing service is reachable from untrusted networks without proper access controls
  4. Confirm device is processing external messages
    Review device logs and service configuration to confirm the device is accepting and processing messages from external sources
    Affected if The device is configured to accept malformed messages from unauthenticated remote sources

You are affected if your Huawei device matches one of the listed models AND runs one of the specific firmware versions AND has message parsing 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 firmware patches for the specific product versions listed. If patches are unavailable, implement network-level access controls and traffic filtering to reduce attack surface exposure.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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