dbcve.org
Ar100 FirmwareOperating system · Huawei

CVE-2017-17151

MEDIUM · 5.9 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 →
68/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 AR100, AR100-S, AR110-S, AR120, AR120-S, AR1200, AR1200-S, AR150, AR150-S, AR160, AR200, AR200-S, AR2200, AR2200-S, AR3200, AR510, DP300, NetEngine16EX, RP200, SRG1300, SRG2300, SRG3300, TE30, TE40, TE50, TE60, TP3106, TP3206, ViewPoint 8660, and ViewPoint 9030 have an insufficient validation vulnerability. Since packet validation is insufficient, an unauthenticated attacker may send special H323 packets to exploit the vulnerability. Successful exploit could allow the attacker to send malicious packets and result in DOS attacks.

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

Multiple Huawei routers and video conferencing devices contain an insufficient validation vulnerability in H323 protocol handling. An unauthenticated remote attacker can send specially crafted H323 packets to trigger improper validation, causing a denial of service condition.

MitigationApply Huawei firmware updates for affected products. If updates are unavailable, consider blocking or restricting H323 protocol traffic at network boundaries unless required for business functions.

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
Ar100 FirmwareOperating system
Affected:= v200r008c20spc700= v200r008c20spc700pwe= v200r008c20spc800= v200r008c20spc800pwe= v200r008c30
Ar100 S FirmwareOperating system
Affected:= v200r007c00spca00= v200r007c00spcb00= v200r008c20= v200r008c20spc700= v200r008c20spc800= v200r008c20spc800pwe= v200r008c30
Ar110 S FirmwareOperating system
Affected:= v200r007c00spc600= v200r007c00spc900= v200r007c00spcb00= v200r008c20spc800= v200r008c30
Ar120 FirmwareOperating system
Affected:= v200r006c10= v200r006c10spc300= v200r006c10spc300pwe= v200r007c00= v200r007c00pwe= v200r007c00spc100= v200r007c00spc200= v200r007c00spc600= v200r007c00spc600pwe= v200r007c00spc900= v200r007c00spc900pwe= v200r007c00spcb00
Ar120 S FirmwareOperating system
Affected:= v200r006c10= v200r006c10spc300= v200r007c00= v200r007c00spc100= v200r007c00spc200= v200r007c00spc600= v200r007c00spc900= v200r007c00spca00= v200r007c00spcb00= v200r008c20= v200r008c20spc700= v200r008c20spc800
Ar1200 FirmwareOperating system
Affected:= v200r006c10= v200r006c10pwe= v200r006c10spc030= v200r006c10spc300= v200r006c10spc300pwe= v200r006c10spc600= v200r006c13= v200r007c00= v200r007c00pwe= v200r007c00spc100= v200r007c00spc200= v200r007c00spc600
Ar1200 S FirmwareOperating system
Affected:= v200r006c10= v200r006c10spc300= v200r007c00= v200r007c00spc100= v200r007c00spc200= v200r007c00spc600= v200r007c00spc900= v200r007c00spcb00= v200r008c20= v200r008c20spc700= v200r008c20spc800= v200r008c20spc800pwe
Ar150 FirmwareOperating system
Affected:= v200r006c10= v200r006c10pwe= v200r006c10spc300= v200r006c10spc300pwe= v200r007c00= v200r007c00pwe= v200r007c00spc100= v200r007c00spc200= v200r007c00spc600= v200r007c00spc600pwe= v200r007c00spc900= v200r007c00spc900pwe

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

CVSS:3.0/AV:N/AC:H/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 router model
    Log into the device via console or SSH and run 'display device' or 'display version' to confirm the model number (Ar100, Ar100 S, Ar110 S, Ar120, Ar120 S, Ar1200, Ar1200 S, or Ar150)
    Affected if The device is one of the listed Huawei AR series models
  2. Check the firmware version
    Run 'display version' or check the bootrom/version information to obtain the exact firmware version string
    Affected if The installed firmware version matches any of the specific versions listed in the affected products section (for example: v200r008c20spc700, v200r007c00, v200r006c10spc300, etc.)
  3. Verify if H323 protocol is enabled
    Run 'display current-configuration | include h323' or check the VoIP/H323 configuration via 'display voip configuration' or 'display ip routing' to see if H323 features are configured
    Affected if H323 protocol is enabled or configured on the device
  4. Check H323 service listener status
    Run 'display tcp status' or 'display ip socket' and look for port 1720 (default H323 RAS port) or check 'display service-port' to see if H323 services are listening
    Affected if The device has H323 ports or services actively listening
  5. Review H323 gateway configuration
    Run 'display current-configuration | include gateway' or 'display voip gateway' to check if the device is configured as an H323 gateway
    Affected if The device is configured as an H323 gateway or has H323 gateway functionality enabled

A defender is affected if they have one of the listed Huawei AR router models running one of the specified firmware versions AND have H323 protocol enabled or configured on the device.

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 firmware updates for affected products. If updates are unavailable, consider blocking or restricting H323 protocol traffic at network boundaries unless required for business functions.

Fix this in Ar100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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