# CVE-2014-9697: Denial of service in n/a

> Remote attackers can cause memory exhaustion and device reboots on Huawei USG firewalls by sending crafted web requests.

- **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:** 17 Oct 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6v5w-79qq-mjhg

## What is CVE-2014-9697?

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

### Official description

Huawei USG9560/9520/9580 before V300R001C01SPC300 allows remote attackers to cause a memory leak or denial of service (memory exhaustion, reboot and MPU switchover) via a crafted website.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2014-9697?

It affects 3 products.


Products: Huawei Usg9520 Firmware, Huawei Usg9560 Firmware, Huawei Usg9580 Firmware.

## How do I fix CVE-2014-9697?

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

## Is CVE-2014-9697 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-8796](https://insights.sbomify.com/CVE-2016-8796/): Denial of service in USG9520,USG9560,USG9580, USG9520 V300R001C01,USG9560 V300R001C01,USG9580 V300R001C01 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9697 and fix it if it is affected.

What it is: CVE-2014-9697 is a high-severity denial of service vulnerability in n/a, published on 17 Oct 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-2014-9697 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-2014-9697/ (Markdown: https://insights.sbomify.com/CVE-2014-9697/index.md)
```

## Sources

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

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