CVE-2020-8670: Race condition in the firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via lo
Noroxi assessment
Priority: Monitor (action score 25/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. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
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
Race condition in the firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access.
- Published
- Jun 9, 2021
- Updated
- Oct 8, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- CWE-362
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.4 / 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.
Running WordPress? Scan your site free with WP Lens
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 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 | bios | cpe:2.3:o:intel:bios |
| intel | core i3-l13g4 | cpe:2.3:h:intel:core_i3-l13g4 |
| intel | core i5-l16g7 | cpe:2.3:h:intel:core_i5-l16g7 |
| intel | core i7-10510u | cpe:2.3:h:intel:core_i7-10510u |
| intel | core i7-10510y | cpe:2.3:h:intel:core_i7-10510y |
| intel | core i7-1060g7 | cpe:2.3:h:intel:core_i7-1060g7 |
| intel | core i7-1060ng7 | cpe:2.3:h:intel:core_i7-1060ng7 |
| intel | core i7-10610u | cpe:2.3:h:intel:core_i7-10610u |
| intel | core i7-1065g7 | cpe:2.3:h:intel:core_i7-1065g7 |
| intel | core i7-1068ng7 | cpe:2.3:h:intel:core_i7-1068ng7 |
| intel | core i7-10700 | cpe:2.3:h:intel:core_i7-10700 |
| intel | core i7-10700e | cpe:2.3:h:intel:core_i7-10700e |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel biosall versions
- netapp aff biosall versions
- netapp cloud backupall versions
- netapp fas biosall versions
- netapp hci compute node biosall versions
- netapp hci storage node biosall versions
- netapp solidfire biosall versions
- siemens simatic field pg m6 firmwareall versions
- siemens simatic ipc427e firmwareall versions
- siemens simatic ipc477e firmwareall versions
- siemens simatic ipc477e pro firmwareall versions
- siemens simatic ipc527g firmwareall versions
- siemens simatic ipc547g firmwareall versions
- siemens simatic ipc627e firmwarebefore 25.02.10
- siemens simatic ipc647e firmwarebefore 25.02.10
- siemens simatic ipc677e firmwarebefore 25.02.10
- siemens simatic ipc847e firmwarebefore 25.02.10
- siemens simatic itp1000 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-2019-14557Buffer overflow in BIOS firmware for 8th, 9th, 10th Generation Intel(R) Core(TM), Intel(R) Celeron(R) Processor 4000 & 5000 Series Processor32Monitor
- CVE-2020-12360Out of bounds read in the firmware for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privileg31Monitor
- CVE-2020-8672Out of bound read in BIOS firmware for 8th, 9th Generation Intel(R) Core(TM), Intel(R) Celeron(R) Processor 4000 Series Processors may allow31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-12359Jun 9, 2021 · Insufficient control flow management in the firmware for some Intel(R) Processors may allow an unauthenticated user to potentially enable es27Monitor
- ← EarlierCVE-2020-24486Jun 9, 2021 · Improper input validation in the firmware for some Intel(R) Processors may allow an authenticated user to potentially enable denial of servi22Monitor
- Later →CVE-2020-8700Jun 9, 2021 · Improper input validation in the firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privi26Monitor
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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0628 · Aug 11, 2021(Siemens Güvenlik Güncellemesi)
- TR-21-0464 · Jun 10, 2021(Intel Güvenlik Zafiyeti)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- Special conditions such as timing or configuration are required.
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
- High
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.