CVE-2017-15349
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 CloudEngine 12800 V100R003C00, V100R005C00, V100R005C10, V100R006C00,CloudEngine 5800 V100R003C00, V100R005C00, V100R005C10, V100R006C00,CloudEngine 6800 V100R003C00, V100R005C00, V100R005C10, V100R006C00,CloudEngine 7800 V100R003C00, V100R005C00, V100R005C10, V100R006C00 have a memory leak vulnerability. An unauthenticated attacker may send specific Resource ReServation Protocol (RSVP) packets to the affected products. Due to not release the memory to handle the packets, successful exploit will result in memory leak of the affected products and lead to a DoS condition.
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 confidenceA memory leak vulnerability exists in Huawei CloudEngine switches (12800, 5800, 6800, 7800 series) when processing specific RSVP packets. The devices fail to release allocated memory when handling these packets, causing memory exhaustion over time and leading to denial of service.
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= v100r003c00= v100r005c00= v100r005c10= v100r006c00= v100r003c00= v100r005c00= v100r005c10= v100r006c00= v100r003c00= v100r005c00= v100r005c10= v100r006c00= v100r003c00= v100r005c00= v100r005c10= v100r006c00CVSS 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
- High
CVSS:3.0/AV:N/AC:L/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 CloudEngine switch modelUse the display device article command or display version command on the switch to confirm the model number (12800, 5800, 6800, or 7800 series)Affected if The device is a Huawei CloudEngine 12800, 5800, 6800, or 7800 series switch
-
Check the installed firmware versionExecute the display version command to retrieve the current software version. Compare it against the affected versions: v100r003c00, v100r005c00, v100r005c10, v100r006c00Affected if The displayed firmware version exactly matches one of the listed affected versions
-
Verify if RSVP protocol is enabledRun the display current-configuration include rsvp command or display ip interface to check whether RSVP (Resource Reservation Protocol) is configured and active on any interfaceAffected if RSVP is enabled and processing traffic on the switch interfaces
-
Check for memory exhaustion symptomsUse the display memory usage command to check for abnormally high memory utilization. Look for steadily increasing memory consumption over time if multiple RSVP packets have been processedAffected if Memory usage is unusually high or continuously increasing without returning to baseline levels
A user is affected if they have a CloudEngine 12800/5800/6800/7800 series switch running any of the exact firmware versions (v100r003c00, v100r005c00, v100r005c10, v100r006c00) with RSVP protocol enabled and processing traffic.
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 the vendor-supplied firmware patches for the affected versions. As a temporary mitigation, consider filtering or blocking RSVP traffic at network perimeter until patches can be applied.
- 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-15349 — 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-15349 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