dbcve.org
S9300 FirmwareOperating system · Huawei

CVE-2014-8570

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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 S9300, S9303, S9306, S9312 with software V100R002; S7700, S7703, S7706, S7712 with software V100R003, V100R006, V200R001, V200R002, V200R003, V200R005; S9300E, S9303E, S9306E, S9312E with software V200R001; S9700, S9703, S9706, S9712 with software V200R002, V200R003, V200R005; S12708, S12712 with software V200R005; 5700HI, 5300HI with software V100R006, V200R001, V200R002, V200R003, V200R005; 5710EI, 5310EI with software V200R002, V200R003, V200R005; 5710HI, 5310HI with software V200R003, V200R005; 6700EI, 6300EI with software V200R005 could cause a leak of IP addresses of devices, related to unintended interface support for VRP MPLS LSP Ping.

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 vulnerability in Huawei VRP-based switches causes unintended IP address leakage through the MPLS LSP Ping diagnostic feature. The feature responds on interfaces where it should be disabled, allowing remote attackers to discover IP addresses of devices on the network via crafted LSP Ping packets.

MitigationDisable or restrict VRP MPLS LSP Ping functionality on untrusted interfaces using ACLs or by disabling the feature where not required, and apply vendor patches for affected software versions.

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:= v100r002= v100r003= v100r006= v200r001= v200r002= v200r003= v200r005
S9303 FirmwareOperating system
Affected:= v100r002= v100r003= v100r006= v200r001= v200r002= v200r003= v200r005
S9306 FirmwareOperating system
Affected:= v100r002= v100r003= v100r006= v200r001= v200r002= v200r003= v200r005
S9312 FirmwareOperating system
Affected:= v100r002= v100r003= v100r006= v200r001= v200r002= v200r003= v200r005
S7700 FirmwareOperating system
Affected:= v100r002= v100r003= v100r006= v200r001= v200r002= v200r003= v200r005
S7703 FirmwareOperating system
Affected:= v100r002= v100r003= v100r006= v200r001= v200r002= v200r003= v200r005
S7706 FirmwareOperating system
Affected:= v100r002= v100r003= v100r006= v200r001= v200r002= v200r003= v200r005
S7712 FirmwareOperating system
Affected:= v100r002= v100r003= v100r006= v200r001= v200r002= v200r003= v200r005

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
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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
    Run 'display device' or check hardware inventory to confirm the switch model is one of: S9300, S9303, S9306, S9312, S7700, S7703, S7706, or S7712
    Affected if Device model is not in the listed affected series
  2. Check firmware version
    Run 'display version' to obtain the VRP firmware version
    Affected if Firmware version matches v100r002, v100r003, v100r006, v200r001, v200r002, v200r003, or v200r005
  3. Verify MPLS is enabled
    Run 'display mpls lsp' or 'display mpls interface' to check if MPLS is configured and active
    Affected if MPLS is enabled and LSPs are configured
  4. Confirm LSP Ping feature status
    Run 'display mpls lsp verbose' or check for LSP Ping related configurations in the MPLS settings
    Affected if LSP Ping functionality is available and responding on interfaces
  5. Check interface exposure
    Review interface configurations with 'display current-configuration interface' focusing on MPLS-enabled interfaces and any ACLs applied to restrict diagnostic features
    Affected if MPLS LSP Ping can be reached on untrusted or external-facing interfaces

You are affected if your device is one of the listed models, runs one of the affected firmware versions, has MPLS enabled with LSP Ping accessible on interfaces where it should be restricted.

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

Disable or restrict VRP MPLS LSP Ping functionality on untrusted interfaces using ACLs or by disabling the feature where not required, and apply vendor patches for affected software versions.

Fix this in S9300 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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