# CVE-2014-6517: Information disclosure in n/a

> Remote attackers can exploit a JAXP vulnerability in Oracle Java SE to disclose sensitive information without authentication or user interaction.

- **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:** Yes
- **Published:** 15 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p339-pvxm-qhgv, UBUNTU-CVE-2014-6517

## What is CVE-2014-6517?

CVE-2014-6517 is a medium-severity vulnerability in Oracle Jdk, published on 15 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in Oracle Java SE 6u81, 7u67, and 8u20; Java SE Embedded 7u60; and Jrockit R27.8.3 and R28.3.3 allows remote attackers to affect confidentiality via vectors related to JAXP.

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

It affects 3 products.


Products: Oracle Jdk, Oracle Jre, Oracle Jrockit.

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

Upgrade to a fixed version.

## Is CVE-2014-6517 being exploited?

There is no known exploitation of CVE-2014-6517 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-6517 and fix it if it is affected.

What it is: CVE-2014-6517 is a medium-severity vulnerability in Oracle Jdk, published on 15 Oct 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-6517 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-6517/ (Markdown: https://insights.sbomify.com/CVE-2014-6517/index.md)
```

## Sources

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

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