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

> Remote attackers can recover TLS session plaintext by exploiting a flaw in the Dual_EC_DRBG implementation of EMC RSA BSAFE-C Toolkits.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 17 Jun 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-32vp-w632-vwm4

## What is CVE-2014-4192?

CVE-2014-4192 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 Dual_EC_DRBG implementation in EMC RSA BSAFE-C Toolkits (aka Share for C and C++) processes certain requests for output bytes by considering only the requested byte count and not the use of cached bytes, which makes it easier for remote attackers to obtain plaintext from TLS sessions by recovering the algorithm's inner state, a different issue than CVE-2007-6755.

Weakness: CWE-310

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

It affects 1 product.


Products: Dell Bsafe Share.

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

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

## Is CVE-2014-4192 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-4191](https://insights.sbomify.com/CVE-2014-4191/): Weak cryptography in n/a (medium 5.0)
- [CVE-2014-4193](https://insights.sbomify.com/CVE-2014-4193/): Weak cryptography in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-4192 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-2014-4192 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-4192/ (Markdown: https://insights.sbomify.com/CVE-2014-4192/index.md)
```

## Sources

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

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