# CVE-2016-10180: Weak cryptography in n/a

> Weak WPS PIN generation using time-based seeding allows attackers to bypass authentication on D-Link routers.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 30 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8vx9-59h6-x23v

## What is CVE-2016-10180?

CVE-2016-10180 is a high-severity vulnerability in n/a, published on 30 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on the D-Link DWR-932B router. WPS PIN generation is based on srand(time(0)) seeding.

Weakness: CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)), CWE-330 (Use of Insufficiently Random Values), CWE-1241 (Use of Predictable Algorithm in Random Number Generator)

## Which versions are affected by CVE-2016-10180?

It affects 1 product.


Products: Dlink Dwr-932b Firmware.

## How do I fix CVE-2016-10180?

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

## Is CVE-2016-10180 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-10180 exists.

## Other vulnerabilities in n/a

- [CVE-2016-10177](https://insights.sbomify.com/CVE-2016-10177/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2016-10178](https://insights.sbomify.com/CVE-2016-10178/): Command injection in n/a (critical 9.8)
- [CVE-2016-10182](https://insights.sbomify.com/CVE-2016-10182/): Command injection in n/a (critical 9.8)
- [CVE-2016-10179](https://insights.sbomify.com/CVE-2016-10179/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2016-10181](https://insights.sbomify.com/CVE-2016-10181/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10180 and fix it if it is affected.

What it is: CVE-2016-10180 is a high-severity vulnerability in n/a, published on 30 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-10180 exists.

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-2016-10180/ (Markdown: https://insights.sbomify.com/CVE-2016-10180/index.md)
```

## Sources

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

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