# CVE-2015-20112: Weak cryptography in RLPx

> Weak cryptography in Ethereum RLPx allows decryption of private network traffic due to reused key, IV, and nonce in CTR streams.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2025
- **Updated:** 30 Jun 2025
- **Also known as:** GHSA-gv8j-3j98-685g

## What is CVE-2015-20112?

CVE-2015-20112 is a low-severity vulnerability in Ethereum RLPx, published on 29 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

RLPx 5 has two CTR streams based on the same key, IV, and nonce. This can facilitate decryption on a private network.

Weakness: CWE-325 (Missing Cryptographic Step)

## Which versions are affected by CVE-2015-20112?


## How do I fix CVE-2015-20112?

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

## Is CVE-2015-20112 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-20112 and fix it if it is affected.

What it is: CVE-2015-20112 is a low-severity vulnerability in Ethereum RLPx, published on 29 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-20112 in the wild and no public exploit code.

Affected product: Ethereum RLPx. 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-2015-20112/ (Markdown: https://insights.sbomify.com/CVE-2015-20112/index.md)
```

## Sources

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

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