dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-15314

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, RP200 V500R002C00SPC200, V600R006C00, TE30 V100R001C10SPC300, V100R001C10SPC500, V100R001C10SPC600, V100R001C10SPC700, V500R002C00SPC200, V500R002C00SPC500, V500R002C00SPC600, V500R002C00SPC700, V500R002C00SPC900, V500R002C00SPCb00, V600R006C00, TE40 V500R002C00SPC600, V500R002C00SPC700, V500R002C00SPC900, V500R002C00SPCb00, V600R006C00, TE50 V500R002C00SPC600, V500R002C00SPC700, V500R002C00SPCb00, V600R006C00, TE60 V100R001C10, V500R002C00, V600R006C00 have a memory leak vulnerability due to memory don't be released when the XML parser process some node fail. An attacker could exploit it to cause memory leak, which may further lead to system exceptions.

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

Memory leak vulnerability in Huawei video conferencing devices (DP300, RP200, TE30/40/50/60) where the XML parser fails to release allocated memory when processing nodes fails. Repeated exploitation causes memory exhaustion leading to system exceptions and potential denial of service.

MitigationApply vendor-supplied firmware patches for the affected versions. If patches unavailable, restrict network access to management interfaces and monitor for abnormal system behavior indicating memory exhaustion.

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:= v500r002c00spc200= v600r006c00
Te30 FirmwareOperating system
Affected:= v100r001c10spc300= v100r001c10spc500= v100r001c10spc600= v100r001c10spc700= v500r002c00spc200= v500r002c00spc500= v500r002c00spc600= v500r002c00spc700= v500r002c00spc900= v500r002c00spcb00= v600r006c00
Te40 FirmwareOperating system
Affected:= v500r002c00spc600= v500r002c00spc700= v500r002c00spc900= v500r002c00spcb00= v600r006c00
Te50 FirmwareOperating system
Affected:= v500r002c00spc600= v500r002c00spc700= v500r002c00spcb00= 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
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 device model
    Access the device CLI or web management interface to retrieve the hardware model (typically via 'display device' command or system information page)
    Affected if Model is DP300, RP200, TE30, TE40, TE50, or TE60
  2. Check firmware version
    Use the device CLI to display the firmware version (typically via 'display version' command or check the About section in the web interface)
    Affected if Version matches any of the affected versions listed for your specific model in the CVE advisory
  3. Observe memory behavior during XML operations
    Monitor system memory usage before and after processing XML-based configurations or management operations using 'display memory' command or system logs
    Affected if Memory continuously increases and does not return to baseline after XML processing completes, indicating the leak is occurring

Device is affected if it is a DP300, RP200, TE30, TE40, TE50, or TE60 running one of the specific firmware versions listed in the affected versions and exhibits abnormal memory growth during or after XML parser operations.

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 affected versions. If patches unavailable, restrict network access to management interfaces and monitor for abnormal system behavior indicating memory exhaustion.

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