Insufficient control flow management in BIOS firmware for 8th, 9th, 10th Generation Intel(R) Core(TM), Intel(R) Celeron(R) Processor 4000 &
Noroxi assessment
Priority: Monitor (action score 22/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.72% (FIRST EPSS); higher than 53.3% of all records.
- Someone on the same network segment can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: edk2 (Debian:12) 0~20200229.4c0f6e34-1; edk2 (Debian:9) 0~20161202.7bbe0b3e-1+deb9u2; ovmf (openSUSE:Tumbleweed) 202105-3.4.
Low priority for now. Upgrade to edk2 (Debian:12) 0~20200229.4c0f6e34-1; edk2 (Debian:9) 0~20161202.7bbe0b3e-1+deb9u2; ovmf (openSUSE:Tumbleweed) 202105-3.4 or later.
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
Insufficient control flow management in BIOS firmware for 8th, 9th, 10th Generation Intel(R) Core(TM), Intel(R) Celeron(R) Processor 4000 & 5000 Series Processors may allow an authenticated user to potentially enable denial of service via adjacent access.
- Published
- Oct 5, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
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 | celeron 4205u | cpe:2.3:h:intel:celeron_4205u |
| intel | celeron 4305u | cpe:2.3:h:intel:celeron_4305u |
| intel | celeron 4305ue | cpe:2.3:h:intel:celeron_4305ue |
| intel | celeron 5205u | cpe:2.3:h:intel:celeron_5205u |
| intel | celeron 5305u | cpe:2.3:h:intel:celeron_5305u |
| intel | core i3 8100 | cpe:2.3:h:intel:core_i3_8100 |
| intel | core i3 8100f | cpe:2.3:h:intel:core_i3_8100f |
| intel | core i3 8100t | cpe:2.3:h:intel:core_i3_8100t |
| intel | core i3 8300 | cpe:2.3:h:intel:core_i3_8300 |
| intel | core i3 8300t | cpe:2.3:h:intel:core_i3_8300t |
| intel | core i3 8350k | cpe:2.3:h:intel:core_i3_8350k |
and 44 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux9.0
- intel biosall 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 BIOS
- 8th, 9th, 10th Generation Intel(R) Core(TM), Intel(R) Celeron(R) Processor 4000 & 5000 Series Processorsaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | edk2 | before 0~20200229.4c0f6e34-1 | 0~20200229.4c0f6e34-1 |
| Debian:9 | edk2 | before 0~20161202.7bbe0b3e-1+deb9u2 | 0~20161202.7bbe0b3e-1+deb9u2 |
| openSUSE:Tumbleweed | ovmf | before 202105-3.4 | 202105-3.4 |
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-2018-3612May 10, 2018 · Intel NUC kits with insufficient input validation in system firmware, potentially allows a local attacker to elevate privileges to System Ma31Monitor
- ← EarlierCVE-2019-14556Oct 5, 2020 · Improper initialization in BIOS firmware for 8th, 9th, 10th Generation Intel(R) Core(TM), Intel(R) Celeron(R) Processor 4000 & 5000 Series P17Monitor
- Later →CVE-2020-0571Oct 5, 2020 · Improper conditions check in BIOS firmware for 8th Generation Intel(R) Core(TM) Processors and Intel(R) Pentium(R) Silver Processor Series m22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:edk2 | 0~20200229.4c0f6e34-1 · Debian:12 | Package registry (OSV) |
| opensuse:ovmf | 202105-3.4 · openSUSE:Tumbleweed | Package registry (OSV) |
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
- Someone on the same network segment 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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.