CVE-2017-15315
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 · uneditedPatch module of Huawei NIP6300 V500R001C20SPC100, V500R001C20SPC200, NIP6600 V500R001C20SPC100, V500R001C20SPC200, Secospace USG6300 V500R001C20SPC100, V500R001C20SPC200, Secospace USG6500 V500R001C20SPC100, V500R001C20SPC200 has a memory leak vulnerability. An authenticated attacker could execute special commands many times, the memory leaking happened, which would cause the device to reset finally.
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 confidenceMemory leak vulnerability in the patch module of Huawei NIP6300, NIP6600, and Secospace USG6300/6500 security appliances. An authenticated attacker can repeatedly execute specific commands to cause memory exhaustion, eventually triggering a device reset.
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= v500r001c20spc100= v500r001c20spc200= v500r001c20spc100= v500r001c20spc200= v500r001c20spc100= v500r001c20spc200= v500r001c20spc100= v500r001c20spc200CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLog into the device CLI or web interface and run 'display device' or check the system information page to confirm the exact model (NIP6300, NIP6600, USG6300, or USG6500)Affected if The device model is NOT one of these four: NIP6300, NIP6600, USG6300, or USG6500 - then you are not affected by this CVE
-
Check the firmware versionRun 'display version' in the CLI or check the firmware version in the web interface to identify the installed versionAffected if The installed version is exactly v500r001c20spc100 or v500r001c20spc200 - these are the affected versions listed in the CVE
-
Verify patch module is accessibleAttempt to access the patch management module via CLI command 'display patch information' or via the web interface under system managementAffected if The patch module is present and accessible to your administrative account - the vulnerability exists in this module
-
Determine if administrative accounts are exposedReview who has administrative or privileged access to the device, check for unnecessary accounts, and verify access lists restrict CLI/web accessAffected if Multiple unauthenticated or untrusted users can reach the administrative interface - the CVE requires an authenticated attacker to trigger the memory leak
-
Review recent device reset eventsRun 'display reboot-info' or check system logs for unexpected reboots or resets that were not initiated by administratorsAffected if The device has experienced unexplained resets or the log shows memory exhaustion as the cause
You are affected if you have a Huawei NIP6300, NIP6600, USG6300, or USG6500 device running firmware version v500r001c20spc100 or v500r001c20spc200, with the patch module accessible to authenticated users.
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 Huawei-supplied firmware patches for the affected versions (V500R001C20SPC100, V500R001C20SPC200). Limit administrative access to trusted personnel only to reduce attack surface.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15315 — 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-15315 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