# CVE-2017-17311: Denial of service in USG2205BSR; USG2220BSR; USG5120BSR; USG5150BSR

> Attackers can cause denial of service on Huawei USG firewalls by sending malformed IPSEC IKEv1 packets due to improper input handling.

- **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:** 21 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m3wg-6jv7-pjg8

## What is CVE-2017-17311?

CVE-2017-17311 is a high-severity denial of service vulnerability in Huawei Technologies Co., Ltd. USG2205BSR; USG2220BSR; USG5120BSR; USG5150BSR, published on 21 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Some Huawei Firewall products USG2205BSR V300R001C10SPC600; USG2220BSR V300R001C00; USG5120BSR V300R001C00; USG5150BSR V300R001C00 have a DoS vulnerability in the IPSEC IKEv1 implementations of Huawei Firewall products. Due to improper handling of the malformed messages, an attacker may sent crafted packets to the affected device to exploit these vulnerabilities. Successful exploit the vulnerability could lead to device deny of service.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 4 products.


Products: Huawei Usg2205bsr Firmware, Huawei Usg2220bsr Firmware, Huawei Usg5120bsr Firmware, Huawei Usg5150bsr Firmware.

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

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

## Is CVE-2017-17311 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. USG2205BSR; USG2220BSR; USG5120BSR; USG5150BSR

- [CVE-2017-17312](https://insights.sbomify.com/CVE-2017-17312/): Denial of service in USG2205BSR; USG2220BSR; USG5120BSR; USG5150BSR (high 7.5)
- [CVE-2017-17305](https://insights.sbomify.com/CVE-2017-17305/): Weak cryptography in USG2205BSR; USG2220BSR; USG5120BSR; USG5150BSR (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17311 is a high-severity denial of service vulnerability in Huawei Technologies Co., Ltd. USG2205BSR; USG2220BSR; USG5120BSR; USG5150BSR, published on 21 Aug 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-17311 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. USG2205BSR; USG2220BSR; USG5120BSR; USG5150BSR. 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-17311/ (Markdown: https://insights.sbomify.com/CVE-2017-17311/index.md)
```

## Sources

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

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