CVE-2017-15348
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 IPS Module V500R001C00, NGFW Module V500R001C00, NIP6300 V500R001C00, NIP6600 V500R001C00, Secospace USG6300 V500R001C00, Secospace USG6500 V500R001C00, Secospace USG6600 V500R001C00, USG9500 V500R001C00 have an insufficient input validation vulnerability. An unauthenticated, remote attacker could send specific MPLS Echo Request messages to the target products. Due to insufficient input validation of some parameters in the messages, successful exploit may cause the device to reset.
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 confidenceThis is an input validation vulnerability in Huawei security products (IPS, NGFW, NIP, USG series) at version V500R001C00. An unauthenticated remote attacker can send specially crafted MPLS Echo Request messages containing malicious parameters that are not properly validated, causing the affected device to reset (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= v500r001c00= v500r001c00= v500r001c00= v500r001c00= v500r001c00= v500r001c00= v500r001c00= v500r001c00CVSS 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 firmware versionRun 'display version' or 'display device' command on the Huawei device console to retrieve the installed firmware versionAffected if The displayed firmware version shows exactly V500R001C00
-
Confirm the product modelRun 'display device' or check the device model identification to confirm it is one of: IPS Module, NGFW Module, NIP6300, NIP6600, USG6300, USG6600, USG9500, or USG6500Affected if The device model matches any of the affected product lines and firmware version is V500R001C00
-
Check if MPLS is enabledRun 'display mpls' or 'display mpls lsp' to check if MPLS functionality is configured and active on the deviceAffected if MPLS is enabled and the firmware version is V500R001C00 - the vulnerability requires MPLS to process the malicious Echo Request messages
-
Verify MPLS interface configurationRun 'display mpls interface' to see which interfaces have MPLS enabled, indicating they can receive MPLS trafficAffected if Any interface has MPLS enabled and the firmware version is V500R001C00
The environment is affected if the device runs firmware version V500R001C00 on any of the listed product models and has MPLS functionality enabled, allowing it to process incoming MPLS Echo Request messages.
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 vendor patches for V500R001C00 or upgrade to a patched firmware version. As a workaround, filter MPLS Echo Request messages from untrusted sources at network boundaries.
- 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-15348 — 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-15348 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