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

> Remote attackers can compromise confidentiality, integrity, and availability in Oracle Java SE via unspecified vectors.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 15 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9vh2-rrjh-87xm

## What is CVE-2014-6456?

CVE-2014-6456 is a critical vulnerability in Oracle Jdk, published on 15 Oct 2014. It can be exploited over the network.

### Official description

Unspecified vulnerability in Oracle Java SE 7u67 and 8u20 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.

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

It affects 2 products.


Products: Oracle Jdk, Oracle Jre.

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

Upgrade to a fixed version.

## Is CVE-2014-6456 being exploited?

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

## Other vulnerabilities in Oracle Jdk

- [CVE-2012-4681](https://insights.sbomify.com/CVE-2012-4681/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-1723](https://insights.sbomify.com/CVE-2012-1723/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-4805](https://insights.sbomify.com/CVE-2015-4805/): Deserialization in n/a (critical 10.0)
- [CVE-2015-4835](https://insights.sbomify.com/CVE-2015-4835/): Other in n/a (critical 10.0)
- [CVE-2015-4843](https://insights.sbomify.com/CVE-2015-4843/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-6456 is a critical vulnerability in Oracle Jdk, published on 15 Oct 2014. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2014-6456 in the wild and no public exploit code.

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

## Sources

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

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