# CVE-2014-2405: Other in n/a

> Unspecified vulnerability in OpenJDK on Debian and Ubuntu systems with unknown impact and attack vectors.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 14 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vjx6-8q4g-9hpf

## What is CVE-2014-2405?

CVE-2014-2405 is a critical vulnerability in Oracle Openjdk, published on 14 May 2014. 

### Official description

Unspecified vulnerability in OpenJDK 6 before 6b31 on Debian GNU/Linux and Ubuntu 12.04 LTS and 10.04 LTS has unknown impact and attack vectors, a different vulnerability than CVE-2014-0462.

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

It affects 1 product.


Products: Oracle Openjdk.

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

Upgrade to a fixed version.

## Is CVE-2014-2405 being exploited?

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

## Other vulnerabilities in Oracle Openjdk

- [CVE-2014-8873](https://insights.sbomify.com/CVE-2014-8873/): Code injection in n/a (critical 10.0)
- [CVE-2014-0462](https://insights.sbomify.com/CVE-2014-0462/): Other in n/a (critical 10.0)
- [CVE-2021-20264](https://insights.sbomify.com/CVE-2021-20264/): Privilege escalation in containers/openjdk (high 7.8)
- [CVE-2014-1876](https://insights.sbomify.com/CVE-2014-1876/): Path traversal in n/a (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2405 is a critical vulnerability in Oracle Openjdk, published on 14 May 2014. 
Exploitation: There is no known exploitation of CVE-2014-2405 in the wild and no public exploit code.

Affected product: Oracle Openjdk. 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-2405/ (Markdown: https://insights.sbomify.com/CVE-2014-2405/index.md)
```

## Sources

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

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