# CVE-2020-7197: SSMC3.7.0.0 is vulnerable to remote authentication bypass.


- **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
- **Fix available:** No
- **Published:** 26 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cvpf-4p84-c3wg

## What is CVE-2020-7197?

CVE-2020-7197 is a critical vulnerability in HPE 3PAR StoreServ Management and Core Software Media, published on 26 Oct 2020. 

### Official description

SSMC3.7.0.0 is vulnerable to remote authentication bypass. HPE StoreServ Management Console (SSMC) 3.7.0.0 is an off node multiarray manager web application and remains isolated from data on the managed arrays. HPE has provided an update to HPE StoreServ Management Console (SSMC) software 3.7.0.0* Upgrade to HPE 3PAR StoreServ Management Console 3.7.1.1 or later.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Hp Storeserv Management Console.

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

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

## Is CVE-2020-7197 being exploited?

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

## Other vulnerabilities in HPE 3PAR StoreServ Management and Core Software Media

- [CVE-2021-29214](https://insights.sbomify.com/CVE-2021-29214/): Code injection in HPE StoreServ Management Console (SSMC); HPE 3PAR StoreServ Management and Core Software Media (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7197 is a critical vulnerability in HPE 3PAR StoreServ Management and Core Software Media, published on 26 Oct 2020. 
Exploitation: There is no known exploitation of CVE-2020-7197 in the wild and no public exploit code.

Affected product: HPE 3PAR StoreServ Management and Core Software Media. 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-7197/ (Markdown: https://insights.sbomify.com/CVE-2020-7197/index.md)
```

## Sources

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

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