NVD / CVE Program· CNA intel

CVE-2021-33076: Improper authentication in firmware for some Intel(R) SSD DC Products may allow an unauthenticated user to potentially enable escalation of

Noroxi assessment

Priority: Monitor (action score 27/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
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.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Improper authentication in firmware for some Intel(R) SSD DC Products may allow an unauthenticated user to potentially enable escalation of privilege via physical access.

MediumCVSS 6.8 · v3.1—No exploit No fix recorded

Auth bypass

Published: Sep 20, 2022
Updated: Jun 16, 2026
EPSS: 0.3% · 23th percentile
CWE: CWE-287

Report tools

JSON

Action score

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: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 6.8
CNA · intel: 5.3; 1.5 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
intel	ssd 600p firmware	cpe:2.3:o:intel:ssd_600p_firmware
intel	ssd 600p	cpe:2.3:h:intel:ssd_600p
intel	ssd 660p firmware	cpe:2.3:o:intel:ssd_660p_firmware
intel	ssd 660p	cpe:2.3:h:intel:ssd_660p
intel	ssd 665p firmware	cpe:2.3:o:intel:ssd_665p_firmware
intel	ssd 665p	cpe:2.3:h:intel:ssd_665p
intel	ssd 670p firmware	cpe:2.3:o:intel:ssd_670p_firmware
intel	ssd 670p	cpe:2.3:h:intel:ssd_670p
intel	ssd 700p firmware	cpe:2.3:o:intel:ssd_700p_firmware
intel	ssd 700p	cpe:2.3:h:intel:ssd_700p
intel	ssd 760p firmware	cpe:2.3:o:intel:ssd_760p_firmware
intel	ssd 760p	cpe:2.3:h:intel:ssd_760p

and 48 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

intel ssd 600p firmwarebefore 122c
intel ssd 660p firmwarebefore 005c
intel ssd 665p firmwarebefore 002c
intel ssd 670p firmwarebefore 003c
intel ssd 700p firmwarebefore 005c
intel ssd 760p firmwarebefore 006c
intel ssd d3-s4510 m.2 firmwarebefore xc311132
intel ssd d3-s4610 m.2 firmwarebefore xc311132
intel ssd d5-p4326 firmwarebefore 8dv1md58
intel ssd d5-p5316 firmwarebefore acv10200
intel ssd d7 p5510 firmwarebefore jcv10200
intel ssd d7 p5600 firmwareall versions
intel ssd dc d4512 firmwarebefore vpv1et0k
intel ssd dc p3100 firmwarebefore 119d
intel ssd dc p4101 firmwarebefore 009d
intel ssd dc p4500 firmwarebefore qdv101b1
intel ssd dc p4501 firmwarebefore qdv101b1
intel ssd dc p4510 edsff firmwarebefore vev10284
intel ssd dc p4510 sff firmwarebefore vdv10184
intel ssd dc p4511 edsff firmwarebefore vev10284

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 DC
- See referencesaffected

Same product

intel: all records

Other highest-scoring records for the same primary product.

CVE-2021-33081Protection mechanism failure in firmware for some Intel(R) SSD DC Products may allow a privileged user to potentially enable information dis
17Monitor
CVE-2021-33079Protection mechanism failure in firmware for some Intel(R) SSD DC Products may allow a privileged user to potentially enable information dis
17Monitor

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.

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, 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

Intel® Vulnerability Disclosure Program Intigriti · disclosure only (VDP)

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)

CWE-287 · Improper Authentication

CVSS vector

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

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

www.solidigm.com/content/dam/newco-aem-site/master/site/support/Solidigm%20SA-000563%20rev1.1.pdf

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records