Improper setting of device configuration in system firmware for Intel(R) NUC kits may allow a privileged user to potentially enable escalati
Improper setting of device configuration in system firmware for Intel(R) NUC kits may allow a privileged user to potentially enable escalation of privilege via physical access.
- Published
- Jan 10, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| intel | nuc kit nuc8i7hnk | cpe:2.3:h:intel:nuc_kit_nuc8i7hnk |
| intel | nuc kit firmware | cpe:2.3:o:intel:nuc_kit_firmware |
| intel | nuc kit d33217gke | cpe:2.3:h:intel:nuc_kit_d33217gke |
| intel | nuc kit d53427rke | cpe:2.3:h:intel:nuc_kit_d53427rke |
| intel | nuc kit d54250wyb | cpe:2.3:h:intel:nuc_kit_d54250wyb |
| intel | nuc kit de3815tybe | cpe:2.3:h:intel:nuc_kit_de3815tybe |
| intel | nuc kit dn2820fykh | cpe:2.3:h:intel:nuc_kit_dn2820fykh |
| intel | nuc kit nuc5cpyh | cpe:2.3:h:intel:nuc_kit_nuc5cpyh |
| intel | nuc kit nuc5i3myhe | cpe:2.3:h:intel:nuc_kit_nuc5i3myhe |
| intel | nuc kit nuc5i5myhe | cpe:2.3:h:intel:nuc_kit_nuc5i5myhe |
| intel | nuc kit nuc5i7ryh | cpe:2.3:h:intel:nuc_kit_nuc5i7ryh |
| intel | nuc kit nuc5pgyh | cpe:2.3:h:intel:nuc_kit_nuc5pgyh |
and 17 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel compute card firmwareall versions
- intel compute stick firmwareall versions
- intel nuc kit firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (oracle). Independent of NVD's CPE analysis and usually ahead of it.
Intel Corporation Intel(R) NUC
- Multiple versions.affected
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-12176Improper input validation in firmware for Intel NUC Kits may allow a privileged user to potentially execute arbitrary code resulting in info32Monitor
- CVE-2019-11094Insufficient input validation in system firmware for Intel (R) NUC Kit may allow an authenticated user to potentially enable escalation of p31Monitor
- CVE-2019-11140Insufficient session validation in system firmware for Intel(R) NUC may allow a privileged user to potentially enable escalation of privileg26Monitor
- CVE-2019-11129Out of bound read/write in system firmware for Intel(R) NUC Kit may allow a privileged user to potentially enable escalation of privilege, d26Monitor
- CVE-2019-11128Insufficient input validation in system firmware for Intel(R) NUC Kit may allow a privileged user to potentially enable escalation of privil26Monitor
- CVE-2019-11127Buffer overflow in system firmware for Intel(R) NUC Kit may allow a privileged user to potentially enable escalation of privilege, denial of26Monitor
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
- Physical access to the device is required.
- Administrator privileges are required.
- 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
- Physical
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:P/AC:L/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.