dbcve.org
Ips Module FirmwareOperating system · Huawei

CVE-2017-17155

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 an out-of-bounds memory access vulnerability due to incompliance with the 4-byte alignment requirement imposed by the MIPS CPU. 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

The vulnerability is an out-of-bounds memory access flaw in the IKEv2 implementation of Huawei IPS and NGFW security modules. The root cause is non-compliance with the 4-byte memory alignment requirement specific to MIPS CPU architecture. When processing certain IKEv2 packets, the code accesses memory at misaligned addresses, allowing an attacker to trigger unauthorized memory reads/writes that can cause system exceptions or potentially execute arbitrary code.

MitigationApply the vendor-supplied firmware patches for the specific product versions (V500R001C00 through V500R001C20SPC300PWE) as listed in Huawei's security advisory. Prioritize patching boundary devices with IKEv2 VPN exposure.

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 device model and firmware version
    Access the device management console or CLI and run the command to display system version information (for example, display version or system-view -> display version). Record the exact firmware version string.
    Affected if The firmware version matches any of the following ranges: v500r001c00, v500r001c00spc200, v500r001c00spc300, v500r001c00spc500, v500r001c00sph303, v500r001c00sph508, v500r001c20, v500r001c20spc100, v500r001c20spc100pwe, v500r001c20spc200, v500r001c20spc200b062, v500r001c20spc200pwe, or related SPC/S
  2. Confirm the IPS or NGFW security module is active
    Check the device status to verify that the IPS module or NGFW module is loaded and running. In the CLI, use commands such as display ipm config or display current-configuration | include ips or display firewall version.
    Affected if The security module is installed and active on a device with an affected firmware version.
  3. Verify IKEv2 protocol is configured
    Examine the VPN or IKE configuration on the device. Use the command display ike peer or display ipsec proposal, or view the current-configuration for IKEv2-related settings (look for ikev2, proposal, or peer configurations).
    Affected if IKEv2 is enabled or configured on the device, creating the condition for the vulnerable code path to be exercised.
  4. Check for exposed IKEv2 VPN interfaces
    Review the network interfaces and VPN bindings to determine if the device is accepting IKEv2 connections from external networks. Use display ip interface or display interface to identify interfaces bound to IKEv2 policies.
    Affected if The device has IKEv2 VPN interfaces that are reachable by network traffic, allowing an attacker to send malicious IKEv2 packets.

The device is affected if it runs an IPS or NGFW module firmware version within the v500r001c00 through v500r001c20 series listed in the advisory AND has IKEv2 protocol 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 the vendor-supplied firmware patches for the specific product versions (V500R001C00 through V500R001C20SPC300PWE) as listed in Huawei's security advisory. Prioritize patching boundary devices with IKEv2 VPN exposure.

Fix this in Ips Module Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-17155 — 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-17155 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