# CVE-2014-9742: Weak cryptography in n/a

> Botan's Miller-Rabin primality test uses a single random base, allowing attackers to bypass cryptographic protections in Diffie-Hellman groups.

- **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:** Yes
- **Published:** 13 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m7rm-rc3m-vmq2, UBUNTU-CVE-2014-9742

## What is CVE-2014-9742?

CVE-2014-9742 is a high-severity vulnerability in n/a, published on 13 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Miller-Rabin primality check in Botan before 1.10.8 and 1.11.x before 1.11.9 improperly uses a single random base, which makes it easier for remote attackers to defeat cryptographic protection mechanisms via a DH group.

Weakness: CWE-310

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

It affects 1 product.


Products: Botan Project Botan.

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

Upgrade to a fixed version.

## Is CVE-2014-9742 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-24115](https://insights.sbomify.com/CVE-2021-24115/): Information disclosure in n/a (critical 9.8)
- [CVE-2018-9127](https://insights.sbomify.com/CVE-2018-9127/): Security feature bypass in n/a (critical 9.8)
- [CVE-2015-7826](https://insights.sbomify.com/CVE-2015-7826/): Security feature bypass in n/a (critical 9.8)
- [CVE-2016-6878](https://insights.sbomify.com/CVE-2016-6878/): Other in n/a (critical 9.8)
- [CVE-2016-9132](https://insights.sbomify.com/CVE-2016-9132/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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