dbcve.org
Ar120 S FirmwareOperating system · Huawei

CVE-2017-17298

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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, V200R008C20, V200R008C30, AR1200 V200R006C10, V200R006C13, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR1200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR150 V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR150-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR160 V200R006C10, V200R006C12, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR200 V200R006C10, V200R007C00, V200R007C01, V200R008C20, V200R008C30, AR200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR2200 V200R006C10, V200R006C13, V200R006C16, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR2200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR3200 V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30, AR3600 V200R006C10, V200R007C00, V200R007C01, V200R008C20, AR510 V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30, DP300 V500R002C00, NetEngine16EX V200R006C10, V200R007C00, V200R008C20, V200R008C30, RP200 V500R002C00, V600R006C00, SRG1300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG2300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG3300 V200R006C10, V200R007C00, V200R008C20, V200R008C30, TE30 V100R001C02, V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00, TP3106 V100R002C00, TP3206 V100R002C00, V100R002C10, ViewPoint 9030 V100R011C02, V100R011C03 have a buffer overflow vulnerability. An unauthenticated, remote attacker may send specially crafted certificates to the affected products. Due to insufficient validation of the certificates, successful exploit may cause buffer overflow and some service abnormal.

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

This vulnerability is a buffer overflow in multiple Huawei AR series routers and related devices. An unauthenticated remote attacker can exploit insufficient validation of specially crafted certificates to trigger a buffer overflow, causing service abnormalities.

MitigationApply the vendor-supplied firmware patches for the specific versions listed. If patches are unavailable, consider network segmentation to limit exposure to untrusted certificate sources.

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= v200r008c20= v200r008c30
Ar1200 FirmwareOperating system
Affected:= v200r006c10= v200r006c13= v200r007c00= v200r007c01= v200r007c02= v200r008c20= v200r008c30
Ar1200 S FirmwareOperating system
Affected:= v200r006c10= v200r007c00= v200r008c20= v200r008c30
Ar150 FirmwareOperating system
Affected:= v200r006c10= v200r007c00= v200r007c01= v200r007c02= v200r008c20= v200r008c30
Ar150 S FirmwareOperating system
Affected:= v200r006c10= v200r007c00= v200r008c20= v200r008c30
Ar160 FirmwareOperating system
Affected:= v200r006c10= v200r006c12= v200r007c00= v200r007c01= v200r007c02= v200r008c20= v200r008c30
Ar200 FirmwareOperating system
Affected:= v200r006c10= v200r007c00= v200r007c01= v200r008c20= v200r008c30
Ar200 S FirmwareOperating system
Affected:= v200r006c10= v200r007c00= v200r008c20= v200r008c30

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
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 device model
    Log into the router CLI and run 'display device' or 'display version' to confirm the exact model number (e.g., AR120-S, AR1200, AR150, AR160, AR200)
    Affected if The model is not one of the following: AR120-S, AR1200, AR1200-S, AR150, AR150-S, AR160, AR200, or AR200-S
  2. Check the firmware version
    Run 'display version' in the router CLI to retrieve the current firmware version
    Affected if The firmware version matches any of these: v200r006c10, v200r006c12, v200r006c13, v200r007c00, v200r007c01, v200r007c02, v200r008c20, or v200r008c30
  3. Verify if certificate-based authentication is enabled
    Run 'display ipsec sa' or 'display ssl vpn' to check for active certificate-based VPN or SSL configurations
    Affected if The device has certificate-based features (IPSec with certificates, SSL VPN, or similar) configured and the firmware version matches an affected version

The environment is affected if the device is a Huawei AR series model (AR120-S, AR1200, AR1200-S, AR150, AR150-S, AR160, AR200, or AR200-S) running any of the listed vulnerable firmware versions with certificate-based services enabled.

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 versions listed. If patches are unavailable, consider network segmentation to limit exposure to untrusted certificate sources.

Fix this in Ar120 S Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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