# CVE-2022-32554: Hardcoded credentials in n/a

> Exposed credentials allow attackers to access the management interface and execute arbitrary instructions with root privileges on affected storage systems.

- **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:** 22 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wxc4-vchh-4j9x

## What is CVE-2022-32554?

CVE-2022-32554 is a critical vulnerability in n/a, published on 22 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pure Storage FlashArray products running Purity//FA 6.2.0 - 6.2.3, 6.1.0 - 6.1.12, 6.0.0 - 6.0.8, 5.3.0 - 5.3.17, 5.2.x and prior Purity//FA releases, and Pure Storage FlashBlade products running Purity//FB 3.3.0, 3.2.0 - 3.2.4, 3.1.0 - 3.1.12, 3.0.x and prior Purity//FB releases are vulnerable to possibly exposed credentials for accessing the product’s management interface. The password may be known outside Pure Storage and could be used on an affected system, if reachable, to execute arbitrary instructions with root privileges. No other Pure Storage products or services are affected. Remediation is available from Pure Storage via a self-serve “opt-in” patch, manual patch application or a software upgrade to an unaffected version of Purity software.

## Which versions are affected by CVE-2022-32554?

It affects 2 products.


Products: Purestorage Purity\/\/Fa, Purestorage Purity\/\/Fb.

## How do I fix CVE-2022-32554?

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

## Is CVE-2022-32554 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-0001](https://insights.sbomify.com/CVE-2024-0001/): Auth bypass in FlashArray (critical 10.0)
- [CVE-2024-0002](https://insights.sbomify.com/CVE-2024-0002/): Auth bypass in FlashArray (critical 10.0)
- [CVE-2024-0003](https://insights.sbomify.com/CVE-2024-0003/): Privilege escalation in FlashArray (critical 9.1)
- [CVE-2024-0004](https://insights.sbomify.com/CVE-2024-0004/): Command injection in FlashArray (critical 9.1)
- [CVE-2024-0005](https://insights.sbomify.com/CVE-2024-0005/): Command injection in FlashArray (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-32554 and fix it if it is affected.

What it is: CVE-2022-32554 is a critical vulnerability in n/a, published on 22 Jun 2022. 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-2022-32554 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-2022-32554/ (Markdown: https://insights.sbomify.com/CVE-2022-32554/index.md)
```

## Sources

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

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