# CVE-2013-6078: Weak cryptography in n/a

> The use of the Dual_EC_DRBG algorithm in RSA BSAFE Toolkits allows attackers to defeat cryptographic protections, requiring an upgrade to secure alternatives.

- **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:** No
- **Published:** 17 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-whq3-8f4v-48fj

## What is CVE-2013-6078?

CVE-2013-6078 is a medium-severity vulnerability in n/a, published on 17 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of EMC RSA BSAFE Toolkits and RSA Data Protection Manager (DPM) 20130918 uses the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm, which makes it easier for context-dependent attackers to defeat cryptographic protection mechanisms by leveraging unspecified "security concerns," aka the ESA-2013-068 issue.  NOTE: this issue has been SPLIT from CVE-2007-6755 because the vendor announcement did not state a specific technical rationale for a change in the algorithm; thus, CVE cannot reach a conclusion that a CVE-2007-6755 concern was the reason, or one of the reasons, for this change.

Weakness: CWE-310

## Which versions are affected by CVE-2013-6078?

It affects 2 products.


Products: Emc Rsa Bsafe Toolkits, Emc Rsa Data Protection Manager.

## How do I fix CVE-2013-6078?

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

## Is CVE-2013-6078 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6078 and fix it if it is affected.

What it is: CVE-2013-6078 is a medium-severity vulnerability in n/a, published on 17 Jun 2014. 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-2013-6078 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-2013-6078/ (Markdown: https://insights.sbomify.com/CVE-2013-6078/index.md)
```

## Sources

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

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