Out-of-bounds read in the BIOS firmware for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of pri
Out-of-bounds read in the BIOS firmware for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via adjacent access.
- Published
- Nov 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 32th percentile
- CWE
- CWE-125
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.0
- CNA · intel
- 4.6
- 3.4 point gap
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 | celeron g1620 | cpe:2.3:h:intel:celeron_g1620 |
| intel | atom x6200fe firmware | cpe:2.3:o:intel:atom_x6200fe_firmware |
| intel | atom x6200fe | cpe:2.3:h:intel:atom_x6200fe |
| intel | atom x6211e firmware | cpe:2.3:o:intel:atom_x6211e_firmware |
| intel | atom x6211e | cpe:2.3:h:intel:atom_x6211e |
| intel | atom x6212re firmware | cpe:2.3:o:intel:atom_x6212re_firmware |
| intel | atom x6212re | cpe:2.3:h:intel:atom_x6212re |
| intel | atom x6413e firmware | cpe:2.3:o:intel:atom_x6413e_firmware |
| intel | atom x6413e | cpe:2.3:h:intel:atom_x6413e |
| intel | atom x6414re firmware | cpe:2.3:o:intel:atom_x6414re_firmware |
| intel | atom x6414re | cpe:2.3:h:intel:atom_x6414re |
| intel | atom x6425e firmware | cpe:2.3:o:intel:atom_x6425e_firmware |
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 atom x6200fe firmwareall versions
- intel atom x6211e firmwareall versions
- intel atom x6212re firmwareall versions
- intel atom x6413e firmwareall versions
- intel atom x6414re firmwareall versions
- intel atom x6425e firmwareall versions
- intel atom x6425re firmwareall versions
- intel atom x6427fe firmwareall versions
- intel celeron 1000m firmwareall versions
- intel celeron 1005m firmwareall versions
- intel celeron 1007u firmwareall versions
- intel celeron 1017u firmwareall versions
- intel celeron 1019y firmwareall versions
- intel celeron 1020e firmwareall versions
- intel celeron 1020m firmwareall versions
- intel celeron 1037u firmwareall versions
- intel celeron 1047ue firmwareall versions
- intel celeron 2000e firmwareall versions
- intel celeron 2002e firmwareall versions
- intel celeron 2950m 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-2023-22329Improper input validation in the BIOS firmware for some Intel(R) Processors may allow an authenticated user to potentially enable denial of 14Monitor
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
- 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:A/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.
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
- security.netapp.com/advisory/ntap-20231221-0008/
- www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00924.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.