# CVE-2015-3913: Denial of service in n/a

> Remote attackers can cause a denial of service by sending crafted ICMP requests to Huawei Campus series switches, requiring vendor patches.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9mrr-8f9q-w3jv

## What is CVE-2015-3913?

CVE-2015-3913 is a high-severity denial of service vulnerability in n/a, published on 8 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The IP stack in multiple Huawei Campus series switch models allows remote attackers to cause a denial of service (reboot) via a crafted ICMP request message.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-3913?

It affects 22 products.


Products: Huawei S12700 Firmware, Huawei S2300 Firmware, Huawei S2350ei Firmware, Huawei S2700 Firmware, Huawei S2750ei Firmware, Huawei S3300 Firmware, Huawei S3700 Firmware, Huawei S5300ei Firmware, Huawei S5300hi Firmware, Huawei S5300li Firmware, Huawei S5300si Firmware, Huawei S5700ei Firmware, Huawei S5700hi Firmware, Huawei S5700li Firmware, Huawei S5700si Firmware, Huawei S5710hi Firmware, Huawei S5720hi Firmware, Huawei S6300ei Firmware, Huawei S6700ei Firmware, Huawei S7700 Firmware and 2 more.

## How do I fix CVE-2015-3913?

No fix has been published for CVE-2015-3913 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-3913 being exploited?

There is no known exploitation of CVE-2015-3913 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2016-4087](https://insights.sbomify.com/CVE-2016-4087/): Command injection in n/a (high 8.1)
- [CVE-2021-22357](https://insights.sbomify.com/CVE-2021-22357/): Denial of service in S12700;S5700;S6700;S7700 (high 7.5)
- [CVE-2019-19397](https://insights.sbomify.com/CVE-2019-19397/): Weak cryptography in S12700;S1700;S2700;S5700;S6700;S7700;S9700 (high 7.5)
- [CVE-2019-5285](https://insights.sbomify.com/CVE-2019-5285/): Denial of service in S12700, S12700, S12700, S12700, S12700, S12700, S12700, S12700, S1700, S1700, S1700, S1700, S1700, S1700, S2300, S2300, S2300, S2300, S2300, S2300, S2300, S2700, S2700, S2700, S2700, S2700, S2700, S2700, S2700, S5300, S5300, S5300, S5300, S5300, S5300, S5300, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S600-E, S600-E, S600-E, S600-E, S600-E, S6300, S6300, S6300, S6300, S6300, S6300, S6300, S6300, S6700, S6700, S6700, S6700, S6700, S6700, S6700, S6700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7900, S7900, S7900, S9300, S9300, S9300, S9300, S9300, S9300, S9300, S9300X, S9300X, S9300X, S9300X, S9700, S9700, S9700, S9700, S9700, S9700, S9700, S9700, S9700 (high 7.5)
- [CVE-2016-8786](https://insights.sbomify.com/CVE-2016-8786/): Denial of service in S12700, S5700, S6700, S7700, S9700 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3913 and fix it if it is affected.

What it is: CVE-2015-3913 is a high-severity denial of service vulnerability in n/a, published on 8 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3913 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-3913/ (Markdown: https://insights.sbomify.com/CVE-2015-3913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-3913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-3913
- OSV: https://osv.dev/vulnerability/CVE-2015-3913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-3913/
Summaries are generated and may contain mistakes; the official description above is the record.