Insufficient control flow management in firmware for some Intel(R) SSD, Intel(R) Optane(TM) SSD and Intel(R) SSD DC Products may allow an un
Insufficient control flow management in firmware for some Intel(R) SSD, Intel(R) Optane(TM) SSD and Intel(R) SSD DC Products may allow an unauthenticated user to potentially enable escalation of privilege via physical access.
- Published
- May 12, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 17th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| intel | optane ssd dc p4800x firmware | cpe:2.3:o:intel:optane_ssd_dc_p4800x_firmware |
| intel | optane ssd dc p4800x | cpe:2.3:h:intel:optane_ssd_dc_p4800x |
| intel | optane ssd dc p4801x firmware | cpe:2.3:o:intel:optane_ssd_dc_p4801x_firmware |
| intel | optane ssd dc p4801x | cpe:2.3:h:intel:optane_ssd_dc_p4801x |
| intel | optane ssd p5800x firmware | cpe:2.3:o:intel:optane_ssd_p5800x_firmware |
| intel | optane ssd p5800x | cpe:2.3:h:intel:optane_ssd_p5800x |
| intel | optane memory h20 with solid state storage firmware | cpe:2.3:o:intel:optane_memory_h20_with_solid_state_storage_firmware |
| intel | optane memory h20 with solid state storage | cpe:2.3:h:intel:optane_memory_h20_with_solid_state_storage |
| intel | optane memory h10 with solid state storage firmware | cpe:2.3:o:intel:optane_memory_h10_with_solid_state_storage_firmware |
| intel | optane memory h10 with solid state storage | cpe:2.3:h:intel:optane_memory_h10_with_solid_state_storage |
| intel | optane ssd 905p firmware | cpe:2.3:o:intel:optane_ssd_905p_firmware |
| intel | optane ssd 905p | cpe:2.3:h:intel:optane_ssd_905p |
and 2 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel optane memory h10 with solid state storage firmwarebefore tgf061k
- intel optane memory h20 with solid state storage firmwarebefore pgf028k
- intel optane ssd 900p firmwarebefore fw600
- intel optane ssd 905p firmwarebefore fw600
- intel optane ssd dc p4800x firmwarebefore e2010600
- intel optane ssd dc p4801x firmwarebefore e2010600
- intel optane ssd p5800x firmwarebefore l0310200
Versions reported by the vendor
Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.
n/a Intel(R) SSD, Intel(R) Optane(TM) SSD and Intel(R) SSD DC Products
- See referencesaffected
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-33080Exposure of sensitive system information due to uncleared debug information in firmware for some Intel(R) SSD DC, Intel(R) Optane(TM) SSD an27Monitor
- CVE-2021-33069Improper 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) SS22Monitor
- CVE-2021-33082Sensitive information in resource not removed before reuse in firmware for some Intel(R) SSD and Intel(R) Optane(TM) SSD Products may allow 18Monitor
- CVE-2021-33078Race condition within a thread in firmware for some Intel(R) Optane(TM) SSD and Intel(R) SSD DC Products may allow a privileged user to pote18Monitor
- CVE-2021-33075Race condition in firmware for some Intel(R) Optane(TM) SSD, Intel(R) Optane(TM) SSD DC and Intel(R) SSD DC Products may allow a privileged 18Monitor
- CVE-2021-33074Protection mechanism failure in firmware for some Intel(R) SSD, Intel(R) SSD DC and Intel(R) Optane(TM) SSD Products may allow an unauthenti18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.