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

> Weak random number generation in Perl Crypt::DSA allows remote attackers to spoof signatures or recover signing keys via brute-force attacks.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 10 Oct 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-3599, GHSA-93qx-3vc3-hx46, MGASA-2013-0289

## What is CVE-2011-3599?

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

### Official description

The Crypt::DSA (aka Crypt-DSA) module 1.17 and earlier for Perl, when /dev/random is absent, uses the Data::Random module, which makes it easier for remote attackers to spoof a signature, or determine the signing key of a signed message, via a brute-force attack.

Weakness: CWE-310

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

It affects 1 product.


Products: Adam Kennedy Crypt-Dsa.

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

Upgrade to a fixed version.

## Is CVE-2011-3599 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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