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

> Attackers can brute force private keys from IBM Java CMS keystores due to weak cryptographic implementation, requiring an upgrade to secure versions.

- **Severity:** Medium 6.4 (`AV:N/AC:L/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:** 2 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-24mr-4mwr-24fg

## What is CVE-2014-3068?

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

### Official description

IBM Java Runtime Environment (JRE) 7 R1 before SR1 FP1 (7.1.1.1), 7 before SR7 FP1 (7.0.7.1), 6 R1 before SR8 FP1 (6.1.8.1), 6 before SR16 FP1 (6.0.16.1), and before 5.0 SR16 FP7 (5.0.16.7) allows attackers to obtain the private key from a Certificate Management System (CMS) keystore via a brute force attack.

Weakness: CWE-255

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

It affects 1 product.


Products: Ibm Java.

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

Upgrade to a fixed version.

## Is CVE-2014-3068 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0485](https://insights.sbomify.com/CVE-2013-0485/): Other in n/a (critical 10.0)
- [CVE-2015-0192](https://insights.sbomify.com/CVE-2015-0192/): Privilege escalation in n/a (critical 9.8)
- [CVE-2013-5456](https://insights.sbomify.com/CVE-2013-5456/): Deserialization in n/a (critical 9.3)
- [CVE-2013-5457](https://insights.sbomify.com/CVE-2013-5457/): Code injection in n/a (critical 9.3)
- [CVE-2013-5458](https://insights.sbomify.com/CVE-2013-5458/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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