CVE-2021-33060: Out-of-bounds write in the BIOS firmware for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of…
Noroxi assessment
Priority: Monitor (action score 31/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.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. 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
Out-of-bounds write in the BIOS firmware for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access.
- Published
- Aug 18, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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 helpAffected 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 | xeon gold 5315y firmware | cpe:2.3:o:intel:xeon_gold_5315y_firmware |
| intel | xeon gold 5315y | cpe:2.3:h:intel:xeon_gold_5315y |
| intel | xeon gold 5317 firmware | cpe:2.3:o:intel:xeon_gold_5317_firmware |
| intel | xeon gold 5317 | cpe:2.3:h:intel:xeon_gold_5317 |
| intel | xeon gold 5318n firmware | cpe:2.3:o:intel:xeon_gold_5318n_firmware |
| intel | xeon gold 5318n | cpe:2.3:h:intel:xeon_gold_5318n |
| intel | xeon gold 5318s firmware | cpe:2.3:o:intel:xeon_gold_5318s_firmware |
| intel | xeon gold 5318s | cpe:2.3:h:intel:xeon_gold_5318s |
| intel | xeon gold 5318y firmware | cpe:2.3:o:intel:xeon_gold_5318y_firmware |
| intel | xeon gold 5318y | cpe:2.3:h:intel:xeon_gold_5318y |
| intel | xeon gold 5320 firmware | cpe:2.3:o:intel:xeon_gold_5320_firmware |
| intel | xeon gold 5320 | cpe:2.3:h:intel:xeon_gold_5320 |
and 132 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel xeon gold 5315y firmwareall versions
- intel xeon gold 5317 firmwareall versions
- intel xeon gold 5318h firmwareall versions
- intel xeon gold 5318n firmwareall versions
- intel xeon gold 5318s firmwareall versions
- intel xeon gold 5318y firmwareall versions
- intel xeon gold 5320 firmwareall versions
- intel xeon gold 5320h firmwareall versions
- intel xeon gold 5320t firmwareall versions
- intel xeon gold 6312u firmwareall versions
- intel xeon gold 6314u firmwareall versions
- intel xeon gold 6326 firmwareall versions
- intel xeon gold 6328h firmwareall versions
- intel xeon gold 6328hl firmwareall versions
- intel xeon gold 6330 firmwareall versions
- intel xeon gold 6330h firmwareall versions
- intel xeon gold 6330n firmwareall versions
- intel xeon gold 6334 firmwareall versions
- intel xeon gold 6336y firmwareall versions
- intel xeon gold 6338 firmwareall versions
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) Processors
- See referencesaffected
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-21216Insufficient granularity of access control in out-of-band management in some Intel(R) Atom and Intel Xeon Scalable Processors may allow a…27Monitor
- CVE-2022-41804Unauthorized error injection in Intel(R) SGX or Intel(R) TDX for some Intel(R) Xeon(R) Processors may allow a privileged user to…26Monitor
- CVE-2022-33196Incorrect default permissions in some memory controller configurations for some Intel(R) Xeon(R) Processors when using Intel(R) Software…26Monitor
Published before and after this one in the same product
- Later →CVE-2022-30539Feb 16, 2023 · Use after free in the BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege…26Monitor
- Later →CVE-2022-33972Feb 16, 2023 · Incorrect calculation in microcode keying mechanism for some 3rd Generation Intel(R) Xeon(R) Scalable Processors may allow a privileged…17Monitor
- Later →CVE-2022-38090Feb 16, 2023 · Improper isolation of shared resources in some Intel(R) Processors when using Intel(R) Software Guard Extensions may allow a privileged…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 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
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/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
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.