# CVE-2019-10174: Use of Externally-Controlled Input to Select Classes or Code in Infinispan

> Attackers can exploit reflection utilities to invoke private methods with elevated privileges, enabling malicious code execution within the application.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h47x-2j37-fw5m, OESA-2024-1667, OESA-2025-1092

## What is CVE-2019-10174?

CVE-2019-10174 is a high-severity vulnerability in Netapp Active Iq Unified Manager, published on 25 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Infinispan such that the invokeAccessibly method from the public class ReflectionUtil allows any application class to invoke private methods in any class with Infinispan's privileges. The attacker can use reflection to introduce new, malicious behavior into the application.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

## Which versions are affected by CVE-2019-10174?

4 open source packages ship an affected version, including org.infinispan:infinispan-core. It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.infinispan:infinispan-core` | Maven | All versions | 8.2.12.Final |
| `org.infinispan:infinispan-core` | Maven | All versions | 8.2.12.Final |
| `org.infinispan:infinispan-core` | Maven | From 9.0.0.Final | 9.4.17.Final |
| `org.infinispan:infinispan-core` | Maven | From 9.0.0.Final | 9.4.17.Final |

Products: Infinispan Infinispan, Netapp Active Iq Unified Manager, Redhat Fuse, Redhat Jboss Data Grid, Redhat Jboss Enterprise Application Platform, Redhat Openshift Application Runtimes, Redhat Single Sign-On.

## How do I fix CVE-2019-10174?

Upgrade org.infinispan:infinispan-core to a fixed version for your release line: 8.2.12.Final or 9.4.17.Final.

## Is CVE-2019-10174 being exploited?

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

## Other vulnerabilities in Netapp Active Iq Unified Manager

- [CVE-2018-1131](https://insights.sbomify.com/CVE-2018-1131/): Deserialization of Untrusted Data in Infinispan (high 8.8)
- [CVE-2017-15089](https://insights.sbomify.com/CVE-2017-15089/): Deserialization of Untrusted Data in Infinispan (high 8.8)
- [CVE-2023-5384](https://insights.sbomify.com/CVE-2023-5384/): Infinispan: credentials returned from configuration as clear text (high 7.2)
- [CVE-2023-3628](https://insights.sbomify.com/CVE-2023-3628/): Infispan: rest bulk ops don't check permissions (medium 6.5)
- [CVE-2020-25711](https://insights.sbomify.com/CVE-2020-25711/): Improper Access Control in infinispan-server-runtime (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10174 and fix it if it is affected.

What it is: CVE-2019-10174 is a high-severity vulnerability in Netapp Active Iq Unified Manager, published on 25 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10174 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.infinispan:infinispan-core (Maven): affected all versions; fixed in 8.2.12.Final
- org.infinispan:infinispan-core (Maven): affected all versions; fixed in 8.2.12.Final
- org.infinispan:infinispan-core (Maven): affected from 9.0.0.Final; fixed in 9.4.17.Final
- org.infinispan:infinispan-core (Maven): affected from 9.0.0.Final; fixed in 9.4.17.Final

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-2019-10174/ (Markdown: https://insights.sbomify.com/CVE-2019-10174/index.md)
```

## Sources

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

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