# CVE-2021-33069: Denial of service in Intel(R) SSD, Intel(R) SSD DC, Intel(R) Optane(TM) SSD and Intel(R) Optane(TM) SSD DC

> A privileged local attacker can cause a denial of service in Intel SSD and Optane drives due to improper resource release in the firmware.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-498v-27pf-8h98

## What is CVE-2021-33069?

CVE-2021-33069 is a medium-severity denial of service vulnerability in Intel(R) SSD, Intel(R) SSD DC, Intel(R) Optane(TM) SSD and Intel(R) Optane(TM) SSD DC, published on 12 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper resource shutdown or release in firmware for some Intel(R) SSD, Intel(R) SSD DC, Intel(R) Optane(TM) SSD and Intel(R) Optane(TM) SSD DC may allow a privileged user to potentially enable denial of service via local access.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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

It affects 7 products.


Products: Intel Optane Memory H10 With Solid State Storage Firmware, Intel Optane Memory H20 With Solid State Storage Firmware, Intel Optane Ssd 900p Firmware, Intel Optane Ssd 905p Firmware, Intel Optane Ssd Dc P4800x Firmware, Intel Optane Ssd Dc P4801x Firmware, Intel Optane Ssd P5800x Firmware.

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

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

## Is CVE-2021-33069 being exploited?

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

## Other vulnerabilities in Intel(R) SSD, Intel(R) SSD DC, Intel(R) Optane(TM) SSD and Intel(R) Optane(TM) SSD DC

- [CVE-2021-33077](https://insights.sbomify.com/CVE-2021-33077/): Privilege escalation in Intel(R) SSD, Intel(R) Optane(TM) SSD and Intel(R) SSD DC Products (medium 6.8)
- [CVE-2021-33080](https://insights.sbomify.com/CVE-2021-33080/): Information disclosure in Intel(R) SSD DC, Intel(R) Optane(TM) SSD and Intel(R) Optane(TM) SSD DC Products (medium 6.8)
- [CVE-2021-33075](https://insights.sbomify.com/CVE-2021-33075/): Race condition in Intel(R) Optane(TM) SSD, Intel(R) Optane(TM) SSD DC and Intel(R) SSD DC Products (medium 4.7)
- [CVE-2021-33078](https://insights.sbomify.com/CVE-2021-33078/): Race condition in Intel(R) Optane(TM) SSD and Intel(R) SSD DC Products (medium 4.7)
- [CVE-2021-33074](https://insights.sbomify.com/CVE-2021-33074/): Information disclosure in Intel(R) SSD, Intel(R) SSD DC and Intel(R) Optane(TM) SSD Products (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-33069 is a medium-severity denial of service vulnerability in Intel(R) SSD, Intel(R) SSD DC, Intel(R) Optane(TM) SSD and Intel(R) Optane(TM) SSD DC, published on 12 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-33069 in the wild and no public exploit code.

Affected product: Intel(R) SSD, Intel(R) SSD DC, Intel(R) Optane(TM) SSD and Intel(R) Optane(TM) SSD DC. 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-33069/ (Markdown: https://insights.sbomify.com/CVE-2021-33069/index.md)
```

## Sources

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

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