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

> An attacker can exploit a low-quality PRNG in hostapd to compromise cryptographic security, potentially bypassing authentication or encryption mechanisms.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Mar 2019
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-10743, DLA-1733-1, GHSA-9m94-6895-mgv3, UBUNTU-CVE-2016-10743

## What is CVE-2016-10743?

CVE-2016-10743 is a high-severity vulnerability in n/a, published on 23 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

hostapd before 2.6 does not prevent use of the low-quality PRNG that is reached by an os_random() function call.

Weakness: CWE-332 (Insufficient Entropy in PRNG)

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

It affects 1 product.


Products: W1.fi Hostapd.

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

Upgrade to a fixed version.

## Is CVE-2016-10743 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-5061](https://insights.sbomify.com/CVE-2019-5061/): Denial of service in W1.f1 (high 7.4)
- [CVE-2019-5062](https://insights.sbomify.com/CVE-2019-5062/): Denial of service in W1.f1 (high 7.4)
- [CVE-2026-58374](https://insights.sbomify.com/CVE-2026-58374/): Memory corruption in hostapd (medium 6.5)
- [CVE-2022-37660](https://insights.sbomify.com/CVE-2022-37660/): Other in n/a (medium 6.5)
- [CVE-2019-11555](https://insights.sbomify.com/CVE-2019-11555/): Null dereference in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-10743 is a high-severity vulnerability in n/a, published on 23 Mar 2019. 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-2016-10743 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-2016-10743/ (Markdown: https://insights.sbomify.com/CVE-2016-10743/index.md)
```

## Sources

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

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