# CVE-2011-2683: Weak cryptography in n/a

> The library uses insecure HTTP for random number seeding, allowing attackers to predict seeds via man-in-the-middle attacks and bypass cryptographic protections.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/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:** 23 Oct 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ppfm-wxvv-g4mw

## What is CVE-2011-2683?

CVE-2011-2683 is a medium-severity vulnerability in n/a, published on 23 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

reseed seeds random numbers from an insecure HTTP request to random.org during installation, which makes it easier for remote attackers to defeat cryptographic protection mechanisms via a man-in-the-middle attack.

Weakness: CWE-254

## Which versions are affected by CVE-2011-2683?

It affects 1 product.


Products: Reseed Project Reseed.

## How do I fix CVE-2011-2683?

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

## Is CVE-2011-2683 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2683 and fix it if it is affected.

What it is: CVE-2011-2683 is a medium-severity vulnerability in n/a, published on 23 Oct 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-2011-2683 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-2011-2683/ (Markdown: https://insights.sbomify.com/CVE-2011-2683/index.md)
```

## Sources

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

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