dbcve.org
Campus S3700hi FirmwareOperating system · Huawei

CVE-2014-4706

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 Campus S3700HI with software V200R001C00SPC300; Campus S5700 with software V200R002C00SPC100; Campus S7700 with software V200R003C00SPC300,V200R003C00SPC500; LSW S9700 with software V200R001C00SPC300,V200R003C00SPC300,V200R003C00SPC500; S2350 with software V200R003C00SPC300; S2750 with software V200R003C00SPC300; S5300 with software V200R001C00SPC300,V200R002C00SPC100,V200R003C00SPC300; S5700 with software V200R001C00SPC300,V200R003C00SPC300; S6300 with software V200R001C00SPC300,V200R002C00SPC100,V200R003C00SPC300; S6700 S3300HI with software V200R001C00SPC300,V200R002C00SPC100,V200R003C00SPC300; S7700 with software V200R001C00SPC300; S9300 with software V200R001C00SPC300,V200R003C00SPC300,V200R003C00SPC500; S9300E with software V200R003C00SPC300,V200R003C00SPC500 allow attackers to keep sending malformed packets to cause a denial of service (DoS) attack, aka a heap overflow.

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 overflow vulnerability in Huawei Campus and LSW switches allows remote attackers to cause denial of service by sending malformed packets. The overflow occurs in packet processing logic, leading to device crash or instability.

MitigationApply vendor-supplied firmware updates; implement network segmentation and packet filtering at perimeter devices to block malformed traffic; monitor for indicators of 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
Campus S3700hi FirmwareOperating system
Affected:= v200r001c00spc300
S5700 FirmwareOperating system
Affected:= v200r001c00spc300= v200r003c00spc300
S6700 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300
S3300hi FirmwareOperating system
Affected:= v200r001c00spc300
S5300 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300
S6300 FirmwareOperating system
Affected:= v200r001c00spc300= v200r002c00spc100= v200r003c00spc300
S9300 FirmwareOperating system
Affected:= v200r001c00spc300= v200r003c00spc300= v200r003c00spc500
S7700 FirmwareOperating system
Affected:= v200r001c00spc300

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 switch model
    Connect to the device CLI and run `display device` or `display version` to confirm the exact model number (e.g., S5700, S6700, S9300, S7700, S3700hi, S3300hi, S5300, S6300)
    Affected if The model matches one of the affected product lines: Campus S3700hi, S3300hi, S5700, S6700, S5300, S6300, S9300, or S7700
  2. Retrieve the firmware version
    Run `display version` in the device CLI. Look for the Software Version field (e.g., V200R001C00SPC300)
    Affected if The displayed firmware version matches any of the affected version strings listed for your model
  3. Compare against affected version list
    Match your firmware version to these specific strings: V200R001C00SPC300, V200R003C00SPC300, V200R002C00SPC100, or V200R003C00SPC500 - exact match required
    Affected if Your installed firmware version exactly matches one of these four version strings for your switch model
  4. Verify the device is network-exposed
    Confirm whether the switch management interface or VLAN interfaces are reachable from untrusted networks
    Affected if The switch has IP connectivity from external or untrusted network segments where malformed packets could be received

You are affected if you have a Huawei switch model from the S3700hi, S3300hi, S5700, S6700, S5300, S6300, S9300, or S7700 series running firmware version V200R001C00SPC300, V200R002C00SPC100, V200R003C00SPC300, or V200R003C00SPC500 and the device is network-reachable.

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; implement network segmentation and packet filtering at perimeter devices to block malformed traffic; monitor for indicators of exploitation.

Fix this in Campus S3700hi Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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