# CVE-2017-10992: Deserialization in n/a

> Unauthenticated attackers can execute arbitrary code via Java deserialization in HPE Storage Essentials.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x427-77qp-c976

## What is CVE-2017-10992?

CVE-2017-10992 is a critical unsafe deserialization vulnerability in n/a, published on 10 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In HPE Storage Essentials 9.5.0.142, there is Unauthenticated Java Deserialization with remote code execution via OS commands in a request to invoker/JMXInvokerServlet, aka PSRT110461.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Hp Storage Essentials.

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

No fix has been published for CVE-2017-10992 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-10992 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4029](https://insights.sbomify.com/CVE-2010-4029/): Other in n/a (high 7.5)
- [CVE-2009-0715](https://insights.sbomify.com/CVE-2009-0715/): Privilege escalation in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10992 is a critical unsafe deserialization vulnerability in n/a, published on 10 Mar 2020. 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-10992 in the wild and no public exploit code.

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

## Sources

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

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