dbcve.org
S9300 FirmwareOperating system · Huawei

CVE-2014-4705

HIGH · 7.5 CVSS v3.0 Published 2018-01-30
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
Multiple heap-based buffer overflows in the eSap software platform in Huawei Campus S9300, S7700, S9700, S5300, S5700, S6300, and S6700 series switches; AR150, AR160, AR200, AR1200, AR2200, AR3200, AR530, NetEngine16EX, SRG1300, SRG2300, and SRG3300 series routers; and WLAN AC6005, AC6605, and ACU2 access controllers allow remote attackers to cause a denial of service (device restart) via a crafted length field in a packet.

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

Heap-based buffer overflow vulnerabilities in Huawei's eSap software platform allow remote attackers to crash affected switches, routers, and WLAN access controllers by sending packets with crafted length fields, causing device restart (denial of service).

MitigationApply vendor-supplied firmware patches for the eSap platform; until patches are available, consider network segmentation and filtering to limit exposure to untrusted network segments.

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
S9300 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc500
S9700 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc500
S7700 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc500
S5300 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300
S5700 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300
S6300 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300
S6700 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300
Ar150 FirmwareOperating system
Affected:= v200r003c00spc100= v200r003c00spc200= v200r003c01spc100= v200r003c01spc300= v200r003c01spc900= v200r005c00spc100= v200r005c00spc200

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 Huawei device model
    Log into the device CLI and run 'display device' or 'display version' to confirm the exact model number (S9300, S9700, S7700, S5300, S5700, S6300, S6700, or Ar150)
    Affected if The device model is not one of the listed affected models
  2. Check the installed firmware version
    Run 'display version' in the device CLI to obtain the current firmware version string
    Affected if The firmware version exactly matches one of the listed affected versions: v200r001c00spc300, v200r002c00spc100, v200r003c00spc500, v200r003c00spc300, v200r003c00spc200, v200r003c01spc100, v200r003c01spc300, v200r003c01spc900, v200r005c00spc100, or v200r005c00spc200
  3. Confirm eSap platform is active
    Run 'display esap status' or check the device configuration for eSap-related modules (display current-configuration | include esap)
    Affected if The eSap platform software module is enabled and running on the device

The device is affected if it is one of the listed Huawei models (S9300, S9700, S7700, S5300, S5700, S6300, S6700, or Ar150) AND runs one of the exact firmware versions specified AND has the eSap platform enabled.

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 patches for the eSap platform; until patches are available, consider network segmentation and filtering to limit exposure to untrusted network segments.

Fix this in S9300 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-4705 — 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-4705 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