# CVE-2017-10125: Privilege escalation in Java

> Physical access allows attackers to compromise Java SE and potentially other products, requiring Java Auto Update to be enabled.

- **Severity:** High 7.1 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Aug 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-w927-cwvw-mr5c, MINI-7jxr-7c6p-3vhc

## What is CVE-2017-10125?

CVE-2017-10125 is a high-severity vulnerability in Netapp Active Iq Unified Manager, published on 8 Aug 2017. It can only be exploited from the same machine or local network, 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: 7u141 and 8u131. Difficult to exploit vulnerability allows physical access to compromise Java SE. While the vulnerability is in Java SE, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE. Note: Applies to deployment of Java where the Java Auto Update is enabled. CVSS 3.0 Base Score 7.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H).

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

It affects 18 products.


Products: 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.

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

Apply the vendor's patch.

## Is CVE-2017-10125 being exploited?

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

## Other vulnerabilities in Netapp Active Iq Unified Manager

- [CVE-2022-31692](https://insights.sbomify.com/CVE-2022-31692/): Spring Security authorization rules can be bypassed via forward or include dispatcher types (critical 9.8)
- [CVE-2022-2526](https://insights.sbomify.com/CVE-2022-2526/): Use after free in systemd-resolved (critical 9.8)
- [CVE-2022-22978](https://insights.sbomify.com/CVE-2022-22978/): Authorization bypass in Spring Security (critical 9.8)
- [CVE-2021-22931](https://insights.sbomify.com/CVE-2021-22931/): Code injection in Node (critical 9.8)
- [CVE-2018-2938](https://insights.sbomify.com/CVE-2018-2938/): Code injection in Java (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10125 is a high-severity vulnerability in Netapp Active Iq Unified Manager, published on 8 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10125 in the wild and no public exploit code.

Affected product: Netapp Active Iq Unified Manager. 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-10125/ (Markdown: https://insights.sbomify.com/CVE-2017-10125/index.md)
```

## Sources

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

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