dbcve.org
Ac6605 FirmwareOperating system · Huawei

CVE-2014-8572

HIGH · 7.5 CVSS v3.0 Published 2017-04-02
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 AC6605 with software V200R001C00; AC6605 with software V200R002C00; ACU with software V200R001C00; ACU with software V200R002C00; S2300, S3300, S2700, S3700 with software V100R006C05 and earlier versions; S5300, S5700, S6300, S6700 with software V100R006, V200R001, V200R002, V200R003, V200R005C00SPC300 and earlier versions; S7700, S9300, S9300E, S9700 with software V100R006, V200R001, V200R002, V200R003, V200R005C00SPC300 and earlier versions could allow remote attackers to send a special SSH packet to the VRP device to cause a denial of service.

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

A denial of service vulnerability exists in Huawei VRP devices where remote attackers can send a specially crafted SSH packet to cause the device to become unresponsive. The vulnerability affects multiple switch models (S2300, S3300, S2700, S3700, S5300, S5700, S6300, S6700, S7700, S9300, S9300E, S9700) and wireless controllers (AC6605, ACU) running specific software versions.

MitigationUpgrade Huawei VRP software to a patched version beyond V200R005C00SPC300 or restrict SSH management access to trusted IP addresses using ACLs as a temporary workaround.

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
Ac6605 FirmwareOperating system
Affected:= ac6605_v200r001c00= ac6605_v200r002c00
Acu FirmwareOperating system
Affected:= acu_v200r001c00= acu_v200r002c00
S Series FirmwareOperating system
Affected:= v100r006c05
S5300 FirmwareOperating system
Affected:<= v200r005c00spc300= v100r006= v200r001= v200r002= v200r003
S5700 FirmwareOperating system
Affected:<= v200r005c00spc300= v100r006= v200r001= v200r002= v200r003
S6700 FirmwareOperating system
Affected:<= v200r005c00spc300= v100r006= v200r001= v200r002= v200r003
S6300 FirmwareOperating system
Affected:<= v200r005c00spc300= v100r006= v200r001= v200r002= v200r003
S7700 FirmwareOperating system
Affected:<= v200r005c00spc300= v100r006= v200r001= v200r002= v200r003

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 the device model
    Run the command `display device` or `display version` on the Huawei VRP device to confirm the product model (e.g., S5300, S5700, AC6605, etc.)
    Affected if The device model matches one of the affected series: S2300, S3300, S2700, S3700, S5300, S5700, S6300, S6700, S7700, S9300, S9300E, S9700, AC6605, or ACU
  2. Identify the firmware version
    Run `display version` to obtain the current VRP software version installed on the device
    Affected if The firmware version matches any of the listed vulnerable versions: v100r006c05, v200r001c00, v200r002c00, v100r006, v200r001, v200r002, v200r003, or any version <= v200r005c00spc300 for the S5300/S5700/S6700/S6300/S7700 series
  3. Check if SSH management is enabled
    Run `display ssh server status` or `display current-configuration | include ssh` to determine whether the SSH server service is enabled on the device
    Affected if SSH server is enabled and configured, as the vulnerability is triggered by specially crafted SSH packets sent to the device
  4. Verify the management interface configuration
    Run `display ip interface` or check the current-configuration for SSH-related service bindings to confirm which interfaces accept SSH management connections
    Affected if SSH service is bound to any management interface (such as vlanif, loopback, or physical ports) that is accessible to untrusted networks

The device is affected if it is one of the listed Huawei VRP models running an affected firmware version AND has SSH management service enabled, allowing remote attackers to send crafted SSH packets to trigger the denial of service condition.

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

Upgrade Huawei VRP software to a patched version beyond V200R005C00SPC300 or restrict SSH management access to trusted IP addresses using ACLs as a temporary workaround.

Fix this in Ac6605 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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