# CVE-2014-9690: Weak cryptography in WS318 V100R001C01B022 and earlier versions

> Weak randomness in WPS PIN generation allows offline brute force attacks, enabling unauthorized internet access via the gateway.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-44xr-76mv-jx32

## What is CVE-2014-9690?

CVE-2014-9690 is a high-severity vulnerability in WS318 V100R001C01B022 and earlier versions, published on 2 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei home gateways WS318 with software V100R001C01B022 and earlier versions are affected by the PIN offline brute force cracking vulnerability of the WPS protocol because the random number generator (RNG) used in the supplier's solution is not random enough. As a result, brute force cracking the PIN code is easier. After an attacker cracks the PIN, the attacker can access the Internet via the cracked device.

Weakness: CWE-332 (Insufficient Entropy in PRNG)

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

It affects 1 product.


Products: Huawei Ws318 Firmware.

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

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

## Is CVE-2014-9690 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9690 is a high-severity vulnerability in WS318 V100R001C01B022 and earlier versions, published on 2 Apr 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-9690 in the wild and no public exploit code.

Affected product: WS318 V100R001C01B022 and earlier versions. 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-9690/ (Markdown: https://insights.sbomify.com/CVE-2014-9690/index.md)
```

## Sources

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

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