dbcve.org
Optane Ssd Dc P4800x FirmwareOperating system · Intel

CVE-2021-33080

MEDIUM · 6.8 CVSS v3.1 Published 2022-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Exposure of sensitive system information due to uncleared debug information in firmware for some Intel(R) SSD DC, Intel(R) Optane(TM) SSD and Intel(R) Optane(TM) SSD DC Products may allow an unauthenticated user to potentially enable information disclosure or escalation of privilege via physical access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Firmware in certain Intel SSD DC and Optane SSD products contains uncleared debug information that exposes sensitive system details. An attacker with physical access to the drive can potentially read this debug data to facilitate information disclosure or privilege escalation.

MitigationApply Intel firmware updates when available. Until patched, restrict physical access to affected storage devices and consider implementing drive encryption as an additional layer of protection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Optane Ssd Dc P4800x FirmwareOperating system
Affected:< e2010600
Optane Ssd Dc P4801x FirmwareOperating system
Affected:< e2010600
Optane Ssd P5800x FirmwareOperating system
Affected:< l0310200
Optane Memory H20 With Solid State Storage FirmwareOperating system
Affected:< pgf028k
Optane Memory H10 With Solid State Storage FirmwareOperating system
Affected:< tgf061k
Optane Ssd 905p FirmwareOperating system
Affected:< fw600
Optane Ssd 900p FirmwareOperating system
Affected:< fw600

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. List installed Intel Optane and SSD drives
    On Linux, run `lspci | grep -i intel` or `lsblk -o NAME,MODEL,TRAN`. On Windows, open Device Manager and expand Storage controllers or look at BIOS/UEFI drive information. Identify any drives matching: Optane DC P4800x, P4801x, P5800x, P905p, P900p, H20, or H10.
    Affected if Any of these specific Intel Optane SSD models are present in the system
  2. Retrieve the firmware version of each identified drive
    Use Intel SSD Toolbox (Windows) or run `smartctl -a /dev/sdX` on Linux to query the firmware revision field. Alternatively, check the drive properties in Device Manager (Windows) or BIOS/UEFI storage information.
    Affected if The firmware version cannot be retrieved (drive may be inaccessible or not supported by diagnostic tools)
  3. Compare firmware version against affected thresholds
    Compare your retrieved firmware version to these limits: P4800x/P4801x < e2010600, P5800x < l0310200, H20 < pgf028k, H10 < tgf061k, 905p/900p < fw600. Note that version strings use different formats; treat any version below the threshold as affected.
    Affected if Your installed firmware version is lower than the threshold listed for your specific model
  4. Assess physical access exposure
    Determine if the affected drive is in a physically accessible location (external USB enclosure, removable laptop drive bay, or system with unrestricted physical access by others).
    Affected if The drive is externally accessible or the system is in an environment with untrusted physical access

You are affected if any Intel Optane SSD model from the list is installed and its firmware version is below the specified threshold and the drive has physical exposure to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Intel firmware updates when available. Until patched, restrict physical access to affected storage devices and consider implementing drive encryption as an additional layer of protection.

Recommended fix High confidence

Upgrade to firmware version e2010600 or later for P4800x/P4801x; l0310200 or later for P5800x; pgf028k or later for H20; tgf061k or later for H10; fw600 or later for 905p/900p

  1. 1. Identify the exact Intel Optane SSD model and current firmware version using the Intel SSD Toolbox or by checking the drive properties in the system BIOS.
  2. 2. Download the latest firmware update utility for your specific model from either support.intel.com (for Intel-branded products) or solidigm.com (for products transferred to Solidigm).
  3. 3. Back up all critical data on the drive before performing firmware update, as with any firmware modification.
  4. 4. Run the firmware update utility and follow the on-screen instructions to apply the update.
  5. 5. Verify the firmware has been successfully updated by checking the new firmware version matches or exceeds: P4800x/P4801x: e2010600, P5800x: l0310200, H20: pgf028k, H10: tgf061k, 905p/900p: fw600
Caveat Firmware updates are low-risk but may require downtime; always backup data before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Optane Ssd Dc P4800x Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing2.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-33080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-33080 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data