# CVE-2017-10115: Information disclosure in Java

> Unauthenticated attackers can access critical data in Java SE via JCE component vulnerabilities, requiring immediate patching.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 8 Aug 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-9v9m-q232-6h4r, MINI-5rxj-98h8-8fm2, UBUNTU-CVE-2017-10115

## What is CVE-2017-10115?

CVE-2017-10115 is a high-severity vulnerability in Debian Debian Linux, published on 8 Aug 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, Java SE Embedded, JRockit component of Oracle Java SE (subcomponent: JCE). Supported versions that are affected are Java SE: 6u151, 7u141 and 8u131; Java SE Embedded: 8u131; JRockit: R28.3.14. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded, JRockit. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Java SE, Java SE Embedded, JRockit accessible data. Note: This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets. It can also be exploited by supplying data to APIs in the specified Component without using sandboxed Java Web Start applications or sandboxed Java applets, such as through a web service. CVSS 3.0 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

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

It affects 28 products.


Products: Debian Debian Linux, Netapp Active Iq Unified Manager, Netapp Cloud Backup, Netapp E-Series Santricity Os Controller, Netapp E-Series Santricity Storage Manager, Netapp Element Software, Netapp Oncommand Balance, Netapp Oncommand Insight, Netapp Oncommand Performance Manager, Netapp Oncommand Shift, Netapp Oncommand Unified Manager, Netapp Plug-in for Symantec Netbackup, Netapp Snapmanager, Netapp Steelstore Cloud Integrated Storage, Netapp Storage Replication Adapter for Clustered Data Ontap, Netapp Vasa Provider for Clustered Data Ontap, Netapp Virtual Storage Console, Oracle Jdk, Oracle Jre, Oracle Jrockit and 8 more.

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

Apply the vendor's patch.

## Is CVE-2017-10115 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10115 and fix it if it is affected.

What it is: CVE-2017-10115 is a high-severity vulnerability in Debian Debian Linux, published on 8 Aug 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-10115 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-10115/ (Markdown: https://insights.sbomify.com/CVE-2017-10115/index.md)
```

## Sources

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

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