CVE-2017-15355
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 · uneditedHuawei DP300, V500R002C00, RP200, V600R006C00, TE30, V100R001C10, V500R002C00,V600R006C00, TE40, V500R002C00, V600R006C00, TE50, V500R002C00,V600R006C00, TE60, V100R001C10, V500R002C00, V600R006C00, TX50,V500R002C00, V600R006C00 have a buffer overflow vulnerability. An attacker may send specially crafted HTTP messages to the affected products. Due insufficient input validation of three different parameters in the messages, successful exploit may cause some service 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 confidenceBuffer overflow vulnerability in Huawei video conferencing products (DP300, TE30/40/50/60, TX50) caused by insufficient input validation of three HTTP message parameters. Successful exploitation with specially crafted HTTP requests can cause service abnormalities.
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= v500r002c00= v600r006c00= v100r001c10= v500r002c00= v600r006c00= v500r002c00= v600r006c00= v500r002c00= v600r006c00= v100r001c10= v500r002c00= v600r006c00= v500r002c00= v600r006c00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Huawei video conferencing product modelAccess the device web interface or CLI and retrieve the system information to confirm the model (DP300, RP200, TE30, TE40, TE50, TE60, or TX50)Affected if The product model is not one of the affected models listed (DP300, RP200, TE30, TE40, TE50, TE60, TX50)
-
Retrieve the installed firmware versionVia the device web interface (typically under System > Device Info or similar) or CLI (display version command), record the exact firmware version stringAffected if The firmware version matches one of the affected versions: v100r001c10, v500r002c00, or v600r006c00 for the identified model
-
Confirm the HTTP management service is enabledCheck the device network settings or service configuration to verify if the HTTP web management interface is enabled and accessibleAffected if HTTP service is enabled and reachable over the network (the vulnerability is triggered via specially crafted HTTP requests)
-
Assess network accessibility of the HTTP serviceDetermine if the HTTP port (typically 80/443) is exposed to untrusted networks or the internet by reviewing firewall rules, ACLs, or network segmentationAffected if The HTTP management interface is accessible from untrusted networks - this is required for exploitation but the vulnerability exists regardless of accessibility
The environment is affected if the device is a Huawei DP300, RP200, TE30, TE40, TE50, TE60, or TX50 running firmware version v100r001c10, v500r002c00, or v600r006c00, with the HTTP service enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied patches for the specific product version (V500R002C00, V600R006C00, etc.). If patches are unavailable, restrict network access to the affected devices and implement input validation on HTTP parameters as a compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2017-15355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-15355 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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