dbcve.org
Ar120 S FirmwareOperating system · Huawei

CVE-2017-8163

MEDIUM · 6.5 CVSS v3.0 Published 2017-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
AR120-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR1200 with software V200R006C10, V200R006C13, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR1200-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR150 with software V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR150-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR160 with software V200R006C10, V200R006C12, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR200 with software V200R006C10, V200R007C00, V200R007C01, V200R008C20, V200R008C30,AR200-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR2200 with software V200R006C10, V200R006C13, V200R006C16PWE, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30,AR2200-S with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,AR3200 with software V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30,AR510 with software V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30,NetEngine16EX with software V200R006C10, V200R007C00, V200R008C20, V200R008C30,SMC2.0 with software V100R003C10, V100R005C00, V500R002C00, V600R006C00,SRG1300 with software V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30,SRG2300 with software V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30,SRG3300 with software V200R006C10, V200R007C00, V200R008C20, V200R008C30 have an out-of-bounds read vulnerability. Due to insufficient input validation, an authenticated, remote attacker could send specially crafted message to the target device.Successful exploit of the vulnerability could cause out-of-bounds read and system crash.

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 is an out-of-bounds read vulnerability in Huawei AR routers (multiple models including AR120-S, AR1200, AR2200, AR3200, AR510, NetEngine16EX) and other devices (SMC2.0, SRG1300, SRG2300, SRG3300). The vulnerability exists due to insufficient input validation, allowing an authenticated remote attacker to send specially crafted messages that trigger an out-of-bounds read, resulting in system crash.

MitigationApply the vendor-supplied patches for the affected software versions. As a compensating control, restrict network access to the device management interfaces and ensure strong authentication is enforced for administrative access.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 device model
    Log into the router CLI and run 'display device' or 'display version' to confirm the hardware model such as AR120-S, AR1200, AR2200, AR3200, AR510, NetEngine16EX, SMC2.0, SRG1300, SRG2300, or SRG3300
    Affected if The model is one of: AR120-S, AR1200, AR2200, AR3200, AR510, NetEngine16EX, SMC2.0, SRG1300, SRG2300, SRG3300
  2. Check the firmware version
    Run 'display version' in the CLI to obtain the firmware version string (for example v200r006c10, v200r007c00, v200r008c20, v200r008c30)
    Affected if The installed firmware version matches any of the versions listed in the affected products table for your model (exact version match required, not range)
  3. Verify management interface accessibility
    Check if remote management protocols (HTTP, HTTPS, SSH, Telnet) are enabled by running 'display ip interface' or 'display service-config' and review access control lists with 'display acl all'
    Affected if The device management interface is exposed to untrusted networks (the vulnerability requires an authenticated attacker to send specially crafted messages)
  4. Confirm authentication is required for the attack vector
    Review the current authentication configuration with 'display current-configuration | include user-interface' and check AAA settings with 'display authentication-scheme'
    Affected if The device allows remote authentication or has user accounts configured for network access (the CVSS indicates the attacker must be authenticated)

Your environment is affected if you are running any of the listed firmware versions on an affected Huawei AR router or related device model AND the device management interface is accessible to an authenticated user.

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 patches for the affected software versions. As a compensating control, restrict network access to the device management interfaces and ensure strong authentication is enforced for administrative access.

Fix this in Ar120 S Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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