# CVE-2020-7138: Privilege escalation in HPE Nimble Storage Hybrid Flash Arrays; Nimble Storage All Flash Arrays; Nimble Storage Secondary Flash Arrays

> Attackers can exploit remote code execution vulnerabilities in HPE Nimble Storage systems to gain elevated privileges on the array.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/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:** No
- **Published:** 19 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jjq3-f9qj-fx43

## What is CVE-2020-7138?

CVE-2020-7138 is a high-severity vulnerability in HPE Nimble Storage Hybrid Flash Arrays; Nimble Storage All Flash Arrays; Nimble Storage Secondary Flash Arrays, published on 19 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Potential remote code execution security vulnerabilities have been identified with HPE Nimble Storage systems that could be exploited by an attacker to gain elevated privileges on the array. The following NimbleOS versions, and all subsequent releases, contain a software fix for this vulnerability: 3.9.3.0 4.5.6.0 5.0.9.0 5.1.4.100

## Which versions are affected by CVE-2020-7138?

It affects 1 product.


Products: Hpe Nimbleos.

## How do I fix CVE-2020-7138?

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

## Is CVE-2020-7138 being exploited?

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

## Other vulnerabilities in HPE Nimble Storage Hybrid Flash Arrays; Nimble Storage All Flash Arrays; Nimble Storage Secondary Flash Arrays

- [CVE-2022-28618](https://insights.sbomify.com/CVE-2022-28618/): Command injection in HPE Nimble Storage Hybrid Flash Arrays; Nimble Storage All Flash Arrays; Nimble Storage Secondary Flash Arrays (critical 9.8)
- [CVE-2019-11996](https://insights.sbomify.com/CVE-2019-11996/): Privilege escalation in HPE Nimble Storage Hybrid Flash Arrays; Nimble Storage All Flash Arrays; Nimble Storage Secondary Flash Arrays (critical 9.8)
- [CVE-2020-7139](https://insights.sbomify.com/CVE-2020-7139/): Information disclosure in HPE Nimble Storage Hybrid Flash Arrays; Nimble Storage All Flash Arrays; Nimble Storage Secondary Flash Arrays (high 8.1)
- [CVE-2022-23705](https://insights.sbomify.com/CVE-2022-23705/): File upload in HPE Nimble Storage Hybrid Flash Arrays; Nimble Storage All Flash Arrays; Nimble Storage Secondary Flash Arrays (high 7.5)
- [CVE-2022-23703](https://insights.sbomify.com/CVE-2022-23703/): Other in HPE Nimble Storage Hybrid Flash Arrays; Nimble Storage All Flash Arrays; Nimble Storage Secondary Flash Arrays (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7138 and fix it if it is affected.

What it is: CVE-2020-7138 is a high-severity vulnerability in HPE Nimble Storage Hybrid Flash Arrays; Nimble Storage All Flash Arrays; Nimble Storage Secondary Flash Arrays, published on 19 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7138 in the wild and no public exploit code.

Affected product: HPE Nimble Storage Hybrid Flash Arrays; Nimble Storage All Flash Arrays; Nimble Storage Secondary Flash Arrays. 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-2020-7138/ (Markdown: https://insights.sbomify.com/CVE-2020-7138/index.md)
```

## Sources

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

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