Improper buffer restrictions in firmware for Intel(R) NUC may allow an authenticated user to potentially enable escalation of privilege via
Improper buffer restrictions in firmware for Intel(R) NUC may allow an authenticated user to potentially enable escalation of privilege via local access. The list of affected products is provided in intel-sa-00343: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00343.html
- Published
- Mar 12, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-120
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
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.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| intel | nuc kit nuc8i7bek firmware | cpe:2.3:o:intel:nuc_kit_nuc8i7bek_firmware |
| intel | nuc kit nuc8i7bek | cpe:2.3:h:intel:nuc_kit_nuc8i7bek |
| intel | nuc 8 enthusiast pc nuc8i7bekqa firmware | cpe:2.3:o:intel:nuc_8_enthusiast_pc_nuc8i7bekqa_firmware |
| intel | nuc 8 enthusiast pc nuc8i7bekqa | cpe:2.3:h:intel:nuc_8_enthusiast_pc_nuc8i7bekqa |
| intel | nuc kit nuc8i7hnk firmware | cpe:2.3:o:intel:nuc_kit_nuc8i7hnk_firmware |
| intel | nuc kit nuc8i7hnk | cpe:2.3:h:intel:nuc_kit_nuc8i7hnk |
| intel | nuc 8 business pc nuc8i7hnkqc firmware | cpe:2.3:o:intel:nuc_8_business_pc_nuc8i7hnkqc_firmware |
| intel | nuc 8 business pc nuc8i7hnkqc | cpe:2.3:h:intel:nuc_8_business_pc_nuc8i7hnkqc |
| intel | nuc 8 mainstream-g kit nuc8i7inh firmware | cpe:2.3:o:intel:nuc_8_mainstream-g_kit_nuc8i7inh_firmware |
| intel | nuc 8 mainstream-g kit nuc8i7inh | cpe:2.3:h:intel:nuc_8_mainstream-g_kit_nuc8i7inh |
| intel | nuc 8 mainstream-g kit nuc8i5inh firmware | cpe:2.3:o:intel:nuc_8_mainstream-g_kit_nuc8i5inh_firmware |
| intel | nuc 8 mainstream-g kit nuc8i5inh | cpe:2.3:h:intel:nuc_8_mainstream-g_kit_nuc8i5inh |
and 128 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel compute stick stck1a32wfc firmwarestck1a32wfc
- intel compute stick stck1a8lfc firmwarestck1a8lfc
- intel compute stick stk1a32sc firmwaresc0045
- intel compute stick stk1aw32sc firmwaresc0045
- intel compute stick stk2m364cc firmwareccsklm30.86a.0062
- intel compute stick stk2m3w64cc firmwareccsklm30.86a.0062
- intel nuc 7 enthusiast pc nuc7i7bnhxg firmwarebnkbl357.86a.0081
- intel nuc 7 essential pc nuc7cjysal firmwarejyglkcpx.86a.0053
- intel nuc 7 home a mini pc nuc7i3bnhxf firmwarebnkbl357.86a.0081
- intel nuc 7 home a mini pc nuc7i5bnhxf firmwarebnkbl357.86a.0081
- intel nuc 7 home a mini pc nuc7i5bnkp firmwarebnkbl357.86a.0081
- intel nuc 8 business pc nuc8i7hnkqc firmwarehnkbli70.86a.0059
- intel nuc 8 enthusiast pc nuc8i7bekqa firmwarebecfl357.86a.0077
- intel nuc 8 home pc nuc8i3cysm firmwarecycnli35.86a.0044
- intel nuc 8 mainstream-g kit nuc8i5inh firmwareinwhl357.0036
- intel nuc 8 mainstream-g kit nuc8i7inh firmwareinwhl357.0036
- intel nuc 8 mainstream-g mini pc nuc8i7inh firmwareinwhl357.0036
- intel nuc 8 rugged kit nuc8cchkr firmwarechaplcel.0047
- intel nuc board d34010wyb firmwarewylpt10h.86a.0054
- intel nuc board d54250wyb firmwarewylpt10h.86a.0054
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.
Intel Intel(R) NUC Firmware
- See advisory https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00343.htmlaffected
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-0526Improper input validation in firmware for Intel(R) NUC may allow a privileged user to potentially enable escalation of privilege via local a26Monitor
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 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-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];if (pkt->len > sizeof(buf)) { return -EINVAL;}memcpy(buf, pkt->data, pkt->len);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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; 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 helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.