dbcve.org
Ar120 S FirmwareOperating system · Huawei

CVE-2017-17257

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 has a memory leak vulnerability in H323 protocol. An unauthenticated, remote attacker could craft malformed packets and send the packets to the affected products. Due to insufficient verification of the packets, successful exploit could cause a memory leak and eventual denial of service (DoS) condition.

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

A memory leak vulnerability exists in the H323 protocol implementation across multiple Huawei AR series routers, USG firewalls, IPS/NGFW modules, and video conferencing devices. An unauthenticated remote attacker can exploit this by sending specially crafted malformed H323 packets. Due to insufficient verification of packet contents, the affected device's memory is not properly released, causing a memory leak that eventually leads to denial of service.

MitigationApply Huawei security patches for the specific product versions in use; if patches are unavailable, block or filter H323 protocol traffic at network boundaries to prevent external exploitation.

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
    Log into the Huawei device and run 'display device' or 'display version' command to confirm the model is an AR120, AR1200, AR1200S, AR150, AR150S, AR160, AR200, or AR200S series device
    Affected if Device model is one of the listed affected models
  2. Check firmware version
    Run 'display version' command and locate the 'VRP (R) software' version line. Compare the version string (e.g., v200r006c10) against the affected version list provided in the CVE advisory
    Affected if Installed firmware version exactly matches one of the versions listed in the CVE (v200r006c10, v200r006c10spc300, v200r006c12, v200r006c13, v200r007c00, v200r007c01, v200r007c02, v200r008c20, v200r008c30)
  3. Verify H323 protocol is enabled
    Run 'display ip interface' or 'display current-configuration | include h323' to check if H323 gateway or H323 protocol features are configured on any interface. Also check 'display service-interface' if available
    Affected if H323 protocol feature is enabled or configured on the device (vulnerability only affects devices with H323 enabled)
  4. Monitor for memory leak symptoms
    Run 'display memory-usage' or 'display cpu-usage' repeatedly over time to observe if memory usage continuously increases without returning to baseline. Check 'display diagnostic-information' for abnormal memory allocation
    Affected if Memory usage shows continuous growth or abnormally high memory consumption that does not correlate with normal traffic patterns

Device is affected if it is an AR series model running one of the listed firmware versions AND has H323 protocol enabled, with memory usage showing abnormal growth patterns.

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 specific product versions in use; if patches are unavailable, block or filter H323 protocol traffic at network boundaries to prevent external exploitation.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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