dbcve.org
Ips Module FirmwareOperating system · Huawei

CVE-2017-17154

HIGH · 7.5 CVSS v3.0 Published 2018-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
IKEv2 in Huawei IPS Module V500R001C00, V500R001C00SPC200, V500R001C00SPC300, V500R001C00SPC500, V500R001C00SPH303, V500R001C00SPH508, V500R001C20, V500R001C20SPC100, V500R001C20SPC100PWE, V500R001C20SPC200, V500R001C20SPC200B062, V500R001C20SPC200PWE, V500R001C20SPC300B078, V500R001C20SPC300PWE, NGFW Module V500R001C00, V500R001C00SPC200, V500R001C00SPC300, V500R001C00SPC500, V500R001C00SPC500PWE, V500R001C00SPH303, V500R001C00SPH508, V500R001C20, V500R001C20SPC100, V500R001C20SPC100PWE, V500R001C20SPC200, V500R001C20SPC200B062, V500R001C20SPC200PWE, V500R001C20SPC300B078, V500R001C20SPC300PWE, NIP6300 V500R001C00, V500R001C00SPC200, V500R001C00SPC300, V500R001C00SPC500, V500R001C00SPH303, V500R001C00SPH508, V500R001C20, V500R001C20SPC100, V500R001C20SPC100PWE, V500R001C20SPC200, V500R001C20SPC200B062, V500R001C20SPC200PWE, V500R001C20SPC300B078, V500R001C20SPC300PWE, NIP6600 V500R001C00, V500R001C00SPC200, V500R001C00SPC300, V500R001C00SPC500, V500R001C00SPH303, V500R001C00SPH508, V500R001C20, V500R001C20SPC100, V500R001C20SPC100PWE, V500R001C20SPC200, V500R001C20SPC200B062, V500R001C20SPC200PWE, V500R001C20SPC300B078, Secospace USG6300 V500R001C00, V500R001C00SPC200, V500R001C00SPC300, V500R001C00SPC500, V500R001C00SPC500PWE, V500R001C00SPH303, V500R001C00SPH508, V500R001C20, V500R001C20SPC100, V500R001C20SPC100PWE, V500R001C20SPC101, V500R001C20SPC200, V500R001C20SPC200B062, V500R001C20SPC200PWE, V500R001C20SPC300B078, V500R001C20SPC300PWE, Secospace USG6500 V500R001C00, V500R001C00SPC200, V500R001C00SPC300, V500R001C00SPC500, V500R001C00SPC500PWE, V500R001C00SPH303, V500R001C00SPH508, V500R001C20, V500R001C20SPC100, V500R001C20SPC100PWE, V500R001C20SPC101, V500R001C20SPC200, V500R001C20SPC200B062, V500R001C20SPC200PWE, V500R001C20SPC300B078, V500R001C20SPC300PWE, Secospace USG6600 V500R001C00, V500R001C00SPC100, V500R001C00SPC200, V500R001C00SPC300, V500R001C00SPC301, V500R001C00SPC500, V500R001C00SPC500PWE, V500R001C00SPH303, V500R001C20, V500R001C20SPC100, V500R001C20SPC100PWE, V500R001C20SPC101, V500R001C20SPC200, V500R001C20SPC200PWE, V500R001C20SPC300, V500R001C20SPC300B078, V500R001C20SPC300PWE, USG9500 V500R001C00, V500R001C00SPC200, V500R001C00SPC300, V500R001C00SPC303, V500R001C00SPC500, V500R001C00SPC500PWE, V500R001C00SPH303, V500R001C00SPH508, V500R001C20, V500R001C20SPC100, V500R001C20SPC100PWE, V500R001C20SPC101, V500R001C20SPC200, V500R001C20SPC200B062, V500R001C20SPC200PWE, V500R001C20SPC300B078, V500R001C20SPC300PWE has a DoS vulnerability due to insufficient input validation. An attacker could exploit it to cause unauthorized memory access, which may further lead to system exceptions.

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 confidence

IKEv2 implementation in multiple Huawei security products contains a vulnerability caused by insufficient input validation. An attacker sending specially crafted IKEv2 packets can trigger unauthorized memory access, leading to denial of service and potential system exceptions.

MitigationApply vendor-provided firmware updates to all affected Huawei security devices. If patches are unavailable, consider restricting IKEv2 traffic at network boundaries or disabling IKEv2 if not required.

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
Ips Module FirmwareOperating system
Affected:= v500r001c00= v500r001c00spc200= v500r001c00spc300= v500r001c00spc500= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc200= v500r001c20spc200b062= v500r001c20spc200pwe
Ngfw Module FirmwareOperating system
Affected:= v500r001c00= v500r001c00spc200= v500r001c00spc300= v500r001c00spc500= v500r001c00spc500pwe= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc200= v500r001c20spc200b062
Nip6300 FirmwareOperating system
Affected:= v500r001c00= v500r001c00spc200= v500r001c00spc300= v500r001c00spc500= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc200= v500r001c20spc200b062= v500r001c20spc200pwe
Nip6600 FirmwareOperating system
Affected:= v500r001c00= v500r001c00spc200= v500r001c00spc300= v500r001c00spc500= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc200= v500r001c20spc200b062= v500r001c20spc200pwe
Secospace Usg6300 FirmwareOperating system
Affected:= v500r001c00= v500r001c00spc200= v500r001c00spc300= v500r001c00spc500= v500r001c00spc500pwe= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc101= v500r001c20spc200
Secospace Usg6500 FirmwareOperating system
Affected:= v500r001c00= v500r001c00spc200= v500r001c00spc300= v500r001c00spc500= v500r001c00spc500pwe= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc101= v500r001c20spc200
Secospace Usg6600 FirmwareOperating system
Affected:= v500r001c00= v500r001c00spc100= v500r001c00spc200= v500r001c00spc300= v500r001c00spc301= v500r001c00spc500= v500r001c00spc500pwe= v500r001c00sph303= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc101
Usg9500 FirmwareOperating system
Affected:= v500r001c00= v500r001c00spc200= v500r001c00spc300= v500r001c00spc303= v500r001c00spc500= v500r001c00spc500pwe= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc101

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Huawei security product model
    Log into the device management interface or check the device label/documentation to determine the exact model (e.g., Nip6300, Usg6600, Usg9500, Ips Module, Ngfw Module)
    Affected if The model is one of: Ips Module, Ngfw Module, Nip6300, Nip6600, Secospace Usg6300, Secospace Usg6500, Secospace Usg6600, or Usg9500
  2. Check the installed firmware version
    Access the device CLI or web interface and run the command to display firmware version (typically 'display version' or check system info in web UI)
    Affected if The firmware version matches any of the listed affected versions: v500r001c00, v500r001c00spc100, v500r001c00spc200, v500r001c00spc300, v500r001c00spc301, v500r001c00spc303, v500r001c00spc500, v500r001c00spc500pwe, v500r001c00sph303, v500r001c00sph508, v500r001c20, v500r001c20spc100, v500r001c20spc1
  3. Verify if IKEv2 is enabled
    Check the IPsec/IKE configuration on the device using 'display ike proposal' or 'display ipsec policy' in CLI, or check VPN settings in web interface
    Affected if IKEv2 protocol is configured or enabled on the device (the vulnerability is triggered by specially crafted IKEv2 packets)
  4. Check for IKEv2 traffic exposure
    Review network firewall rules and interfaces to determine if the device is directly exposed to incoming IKEv2 traffic from untrusted networks
    Affected if The device accepts IKEv2 packets from external networks (this indicates potential attack surface)

The environment is affected if the device is a Huawei security product (Ips Module, Ngfw Module, Nip6300, Nip6600, Usg6300, Usg6500, Usg6600, or Usg9500) running any of the listed firmware versions AND has IKEv2 enabled and exposed to network traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided firmware updates to all affected Huawei security devices. If patches are unavailable, consider restricting IKEv2 traffic at network boundaries or disabling IKEv2 if not required.

Fix this in Ips Module Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-17154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-17154 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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