# CVE-2017-3259: Information disclosure in Java SE

> An unauthenticated attacker can read a subset of Java SE accessible data via network access in client deployments running untrusted code.

- **Severity:** Low 3.7 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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:** 27 Jan 2017
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-2fjh-pp98-gvch, MINI-2q6r-j493-cc76

## What is CVE-2017-3259?

CVE-2017-3259 is a low-severity vulnerability in Oracle Jdk, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Deployment). Supported versions that are affected are Java SE: 6u131, 7u121 and 8u112. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Java SE accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS v3.0 Base Score 3.7 (Confidentiality impacts).

## Which versions are affected by CVE-2017-3259?

It affects 2 products.


Products: Oracle Jdk, Oracle Jre.

## How do I fix CVE-2017-3259?

Upgrade to a fixed version.

## Is CVE-2017-3259 being exploited?

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

What it is: CVE-2017-3259 is a low-severity vulnerability in Oracle Jdk, published on 27 Jan 2017. 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-2017-3259 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-2017-3259/ (Markdown: https://insights.sbomify.com/CVE-2017-3259/index.md)
```

## Sources

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

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