dbcve.org
Ar120 S FirmwareOperating system · Huawei

CVE-2017-17254

HIGH · 7.5 CVSS v3.0 Published 2018-04-24
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, 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 V200R006C10SPC300, 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, V200R006C16PWE, 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, V200R007C00SPC180T, V200R008C20, V200R008C30, DP300 V500R002C00, IPS Module V100R001C10SPC200, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, NGFW Module V100R001C10SPC200, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R002C00, V500R002C10, NIP6300 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6600 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6800 V500R001C50, NetEngine16EX V200R006C10, V200R007C00, V200R008C20, V200R008C30, RSE6500 V500R002C00, SRG1300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG2300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG3300 V200R006C10, V200R007C00, V200R008C20, V200R008C30, SVN5600 V200R003C00, V200R003C10, SVN5800 V200R003C00, V200R003C10, SVN5800-C V200R003C00, V200R003C10, SeMG9811 V300R001C01, Secospace USG6300 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6500 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6600 V100R001C00SPC200, V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, V500R001C60, TE30 V100R001C02, V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00, TP3106 V100R002C00, TP3206 V100R002C00, V100R002C10, USG6000V V500R001C20, USG9500 V500R001C00, V500R001C20, V500R001C30, V500R001C50, USG9520 V300R001C01, V300R001C20, USG9560 V300R001C01, V300R001C20, USG9580 V300R001C01, V300R001C20, VP9660 V500R002C00, V500R002C10, ViewPoint 8660 V100R008C03, ViewPoint 9030 V100R011C02 have a null pointer dereference vulnerability in H323 protocol. An unauthenticated, remote attacker could craft malformed packets and send the packets to the affected products. Due to insufficient validation of packets, which could be exploited to cause process 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 · high confidence

This is a null pointer dereference vulnerability in the H323 protocol implementation across numerous Huawei AR router, USG security gateway, NIP intrusion prevention, and video conferencing products. An unauthenticated remote attacker can send specially crafted malformed H323 packets to trigger insufficient validation, causing a null pointer dereference that leads to process crash (denial of service).

MitigationApply vendor-supplied firmware updates for the specific product versions listed. As an interim control, block or restrict H323 protocol traffic (port 1720 and related ports) at network boundaries to prevent unauthenticated external attackers from reaching affected devices.

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:= v200r006c10spc300= 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
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 platform
    Access the device via console, SSH, or web interface and run 'display device' or 'display version' to confirm the Huawei product model (e.g., AR120S, AR1200, AR150, AR160, AR200)
    Affected if The device model is one of the affected AR series models listed in the CVE (Ar120S, Ar1200, Ar1200S, Ar150, Ar150S, Ar160, Ar200, Ar200S)
  2. Check installed firmware version
    Run 'display version' or 'display bootrom' to retrieve the current firmware version; compare against the affected versions: v200r006c10, v200r006c12, v200r006c13, v200r006c10spc300, v200r007c00, v200r007c01, v200r007c02, v200r008c20, v200r008c30
    Affected if The installed firmware version matches any of the specific versions listed in the CVE for your model
  3. Verify H323 protocol is enabled
    Run 'display ip interface' or 'display current-configuration' and search for H323-related configurations (e.g., 'h323 enable', 'protocol h323', or VoIP/H323 gateway settings); check if port 1720 is listed as open
    Affected if H323 protocol is explicitly enabled or configured on the device, as the vulnerability only triggers when H323 processing is active
  4. Confirm network exposure to H323 traffic
    Check firewall or access control lists to determine if inbound H323 traffic (port 1720/TCP and related UDP ports) from untrusted networks is permitted; run 'display firewall zone' or 'displayacl' to review perimeter rules
    Affected if The device H323 interface is reachable from untrusted network segments, allowing unauthenticated malformed H323 packets to reach the device

You are affected if you are running one of the listed Huawei AR models on any of the specified firmware versions AND H323 protocol is enabled AND the device is network-accessible to potential attackers sending malformed H323 packets.

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 vendor-supplied firmware updates for the specific product versions listed. As an interim control, block or restrict H323 protocol traffic (port 1720 and related ports) at network boundaries to prevent unauthenticated external attackers from reaching affected devices.

Fix this in Ar120 S Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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