# CVE-2021-29873: IBM Flash System 900 could allow an authenticated attacker to obtain sensitive information and cause a denial of service due to a restricted


- **Severity:** High 8.8 (`CVSS:3.0/A:H/AV:N/I:H/PR:L/C:H/S:U/UI:N/AC:L/E:U/RC:C/RL:O`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4j24-8q6f-65hw

## What is CVE-2021-29873?

CVE-2021-29873 is a high-severity vulnerability in IBM FlashSystem 900, published on 21 Oct 2021. 

### Official description

IBM Flash System 900 could allow an authenticated attacker to obtain sensitive information and cause a denial of service due to a restricted shell escape vulnerability. IBM X-Force ID: 206229.

## Which versions are affected by CVE-2021-29873?

It affects 10 products.


Products: Ibm Flashsystem 9000 Firmware, Ibm Flashsystem 9100 Firmware, Ibm San Volume Controller Firmware, Ibm Spectrum Virtualize, Ibm Spectrum Virtualize for Public Cloud, Ibm Storwize V3500 Software, Ibm Storwize V3700 Software, Ibm Storwize V5000 Software, Ibm Storwize V5100 Software, Ibm Storwize V7000 Software.

## How do I fix CVE-2021-29873?

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

## Is CVE-2021-29873 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29873 and fix it if it is affected.

What it is: CVE-2021-29873 is a high-severity vulnerability in IBM FlashSystem 900, published on 21 Oct 2021. 
Exploitation: There is no known exploitation of CVE-2021-29873 in the wild and no public exploit code.

Affected product: IBM FlashSystem 900. 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-2021-29873/ (Markdown: https://insights.sbomify.com/CVE-2021-29873/index.md)
```

## Sources

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

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