# CVE-2017-15349: Denial of service in CloudEngine 12800,CloudEngine 5800,CloudEngine 6800,CloudEngine 7800,

> Unauthenticated attackers can cause a denial of service on Huawei CloudEngine switches by sending specific RSVP packets that trigger a memory leak.

- **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:** 15 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hqf3-w8jr-9qmr

## What is CVE-2017-15349?

CVE-2017-15349 is a high-severity denial of service vulnerability in Huawei Technologies Co., Ltd. CloudEngine 12800,CloudEngine 5800,CloudEngine 6800,CloudEngine 7800,, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei CloudEngine 12800 V100R003C00, V100R005C00, V100R005C10, V100R006C00,CloudEngine 5800 V100R003C00, V100R005C00, V100R005C10, V100R006C00,CloudEngine 6800 V100R003C00, V100R005C00, V100R005C10, V100R006C00,CloudEngine 7800 V100R003C00, V100R005C00, V100R005C10, V100R006C00 have a memory leak vulnerability. An unauthenticated attacker may send specific Resource ReServation Protocol (RSVP) packets to the affected products. Due to not release the memory to handle the packets, successful exploit will result in memory leak of the affected products and lead to a DoS condition.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

## Which versions are affected by CVE-2017-15349?

It affects 4 products.


Products: Huawei Cloudengine 12800 Firmware, Huawei Cloudengine 5800 Firmware, Huawei Cloudengine 6800 Firmware, Huawei Cloudengine 7800 Firmware.

## How do I fix CVE-2017-15349?

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

## Is CVE-2017-15349 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. CloudEngine 12800,CloudEngine 5800,CloudEngine 6800,CloudEngine 7800,

- [CVE-2016-6178](https://insights.sbomify.com/CVE-2016-6178/): Other in n/a (critical 9.8)
- [CVE-2020-9207](https://insights.sbomify.com/CVE-2020-9207/): Auth bypass in CloudEngine 12800 (high 7.8)
- [CVE-2021-40008](https://insights.sbomify.com/CVE-2021-40008/): Denial of service in CloudEngine 12800;CloudEngine 5800;CloudEngine 6800;CloudEngine 7800 (high 7.5)
- [CVE-2021-22328](https://insights.sbomify.com/CVE-2021-22328/): Denial of service in CloudEngine 12800;CloudEngine 5800;CloudEngine 6800;CloudEngine 7800 (high 7.5)
- [CVE-2021-22332](https://insights.sbomify.com/CVE-2021-22332/): Use after free in CloudEngine 12800;CloudEngine 5800;CloudEngine 6800;CloudEngine 7800 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15349 and fix it if it is affected.

What it is: CVE-2017-15349 is a high-severity denial of service vulnerability in Huawei Technologies Co., Ltd. CloudEngine 12800,CloudEngine 5800,CloudEngine 6800,CloudEngine 7800,, published on 15 Feb 2018. 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-2017-15349 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. CloudEngine 12800,CloudEngine 5800,CloudEngine 6800,CloudEngine 7800,. 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-2017-15349/ (Markdown: https://insights.sbomify.com/CVE-2017-15349/index.md)
```

## Sources

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

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