CVE-2017-17199
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 V500R002C00; V600R006C00; TE30 V100R001C10; V500R002C00; V600R006C00; TE40 V500R002C00; V600R006C00; TE50 V500R002C00; V600R006C00; TE60 V100R001C10; V500R002C00; V600R006C00 have an out-of-bounds read vulnerability due to the improper processing of malformed H323 messages. A remote attacker that controls a server could exploit this vulnerability by sending malformed H323 reply messages to a target device. Successful exploit could make the device read out of bounds and probably make a service unavailable.
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 confidenceAn out-of-bounds read vulnerability exists in the H323 protocol implementation on multiple Huawei video conferencing devices (DP300, RP200, TE30-TE60). The vulnerability stems from improper processing of malformed H323 reply messages, allowing a remote attacker controlling a malicious server to send specially crafted messages that cause the device to read beyond allocated buffer boundaries.
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= v500r002c00= v600r006c00= v100r001c10= v500r002c00= v600r006c00= v500r002c00= v600r006c00= v500r002c00= v600r006c00= v100r001c10= 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device administrative interface or check the device label to confirm the model is one of: DP300, RP200, TE30, TE40, TE50, or TE60Affected if The device is not one of these six models, then it is not affected by this CVE
-
Determine the firmware versionLog into the device CLI or web interface and run the command to display firmware version (for example: 'display version' or check system information page)Affected if The installed version matches any of these exact versions: v100r001c10, v500r002c00, or v600r006c00 for the identified model
-
Verify H323 protocol is enabledCheck the device network configuration or protocol settings to determine if H323 is enabled and listening for H323 trafficAffected if H323 is actively enabled and the device processes H323 messages, making it vulnerable to specially crafted malformed replies
-
Confirm network exposure to untrusted H323 sourcesReview firewall rules, ACLs, or network segmentation to determine if the device accepts H323 connections from untrusted or external network sourcesAffected if The device can receive H323 traffic from untrusted or attacker-controlled servers, enabling the malformed message attack vector
The device is affected if it is a Huawei DP300, RP200, TE30, TE40, TE50, or TE60 running firmware version v100r001c10, v500r002c00, or v600r006c00 with H323 protocol enabled and accessible to untrusted network sources.
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 firmware updates for the affected versions. If updates are unavailable, restrict H323 traffic to trusted endpoints via firewall rules or ACLs to reduce attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17199 — 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-17199 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