dbcve.org
Ar120 S FirmwareOperating system · Huawei

CVE-2017-17299

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
Huawei AR120-S V200R006C10, V200R007C00, AR1200 V200R006C10, V200R006C13, V200R007C00, V200R007C02, AR1200-S V200R006C10, V200R007C00, V200R008C20, AR150 V200R006C10, V200R007C00, V200R007C02, AR150-S V200R006C10, V200R007C00, AR160 V200R006C10, V200R006C12, V200R007C00S, V200R007C02, AR200 V200R006C10, V200R007C00, AR200-S V200R006C10, V200R007C00, AR2200 V200R006C10, V200R006C13, V200R006C16, V200R007C00, V200R007C02, AR2200-S V200R006C10, V200R007C00, V200R008C20, AR3200 V200R006C10, V200R006C11, V200R007C00, V200R007C02, AR3600 V200R006C10, V200R007C00, AR510 V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, IPS Module V500R001C30, NIP6300 V500R001C30, NetEngine16EX V200R006C10, V200R007C00 have an insufficient input validation vulnerability. An unauthenticated, remote attacker may send crafted IKE V2 messages to the affected products. Due to the insufficient validation of the messages, successful exploit will cause invalid memory access and result in a denial of service on the affected products.

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 confidence

This vulnerability exists in the IKE V2 message handling component of multiple Huawei AR router series and IPS modules. An unauthenticated remote attacker can send specially crafted IKE V2 packets that trigger insufficient input validation, leading to invalid memory access and a denial of service condition.

MitigationApply Huawei security patches for the affected firmware versions. If patches are unavailable, consider implementing network-level filtering of IKE traffic from untrusted sources or disabling IKE VPN services 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
Ar120 S FirmwareOperating system
Affected:= v200r006c10= v200r007c00
Ar1200 FirmwareOperating system
Affected:= v200r006c10= v200r006c13= v200r007c00= v200r007c02
Ar1200 S FirmwareOperating system
Affected:= v200r006c10= v200r007c00= v200r008c20
Ar150 FirmwareOperating system
Affected:= v200r006c10= v200r007c00= v200r007c02
Ar150 S FirmwareOperating system
Affected:= v200r006c10= v200r007c00
Ar160 FirmwareOperating system
Affected:= v200r006c10= v200r006c12= v200r007c00s= v200r007c02
Ar200 FirmwareOperating system
Affected:= v200r006c10= v200r007c00
Ar200 S FirmwareOperating system
Affected:= v200r006c10= v200r007c00

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
    Log into the router and run 'display device' or 'display version' to confirm the device is a Huawei AR series router (AR120-S, AR1200, AR1200-S, AR150, AR150-S, AR160, AR200, or AR200-S)
    Affected if Device is not a Huawei AR series router - not affected by this CVE
  2. Check firmware version
    Run 'display version' on the router CLI and locate the VRP (Versatile Routing Platform) firmware version string (typically shown as v200rXXXXcXX)
    Affected if Firmware version does not match any of these: v200r006c10, v200r006c12, v200r006c13, v200r007c00, v200r007c00s, v200r007c02, or v200r008c20 - not affected
  3. Verify IKE V2 is enabled
    Run 'display ike sa' or 'display ipsec sa' to check for active IKE Security Associations. Also run 'display ipsec policy' to see if any IPSec policies using IKE are configured
    Affected if No IKE v2 policies configured and no active IKE Security Associations exist - not affected (the vulnerable component is not in use)

You are affected if your Huawei AR router runs one of the listed firmware versions AND has IKE V2 IPSec VPN policies configured or active connections.

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 Huawei security patches for the affected firmware versions. If patches are unavailable, consider implementing network-level filtering of IKE traffic from untrusted sources or disabling IKE VPN services if not required.

Fix this in Ar120 S Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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