CVE-2019-14610: Improper access control in firmware for Intel(R) NUC(R) may allow an authenticated user to potentially enable escalation of privilege via lo
Noroxi assessment
Priority: Monitor (action score 31/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.33% (FIRST EPSS).
- 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.
- According to the record, no fixed version is available yet.
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
Improper access control in firmware for Intel(R) NUC(R) may allow an authenticated user to potentially enable escalation of privilege via local access.
- Published
- Dec 16, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- —
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%
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 | nuc 8 mainstream game kit firmware | cpe:2.3:o:intel:nuc_8_mainstream_game_kit_firmware |
| intel | nuc 8 mainstream game kit | cpe:2.3:h:intel:nuc_8_mainstream_game_kit |
| intel | nuc 8 mainstream game mini computer firmware | cpe:2.3:o:intel:nuc_8_mainstream_game_mini_computer_firmware |
| intel | nuc 8 mainstream game mini computer | cpe:2.3:h:intel:nuc_8_mainstream_game_mini_computer |
| intel | nuc8i7bek firmware | cpe:2.3:o:intel:nuc8i7bek_firmware |
| intel | nuc8i7bek | cpe:2.3:h:intel:nuc8i7bek |
| intel | cd1p64gk firmware | cpe:2.3:o:intel:cd1p64gk_firmware |
| intel | cd1p64gk | cpe:2.3:h:intel:cd1p64gk |
| intel | nuc8i3cysm firmware | cpe:2.3:o:intel:nuc8i3cysm_firmware |
| intel | nuc8i3cysm | cpe:2.3:h:intel:nuc8i3cysm |
| intel | nuc8i7hnk firmware | cpe:2.3:o:intel:nuc8i7hnk_firmware |
| intel | nuc8i7hnk | cpe:2.3:h:intel:nuc8i7hnk |
and 26 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel cd1iv128mk firmwarebefore 0038
- intel cd1m3128mk firmwarebefore 0058
- intel cd1p64gk firmwarebefore 0053
- intel d34010wyb firmwarebefore 0054
- intel de3815tybe firmwarebefore 0024
- intel nuc 8 mainstream game kit firmwarebefore 0036
- intel nuc 8 mainstream game mini computer firmwarebefore 0036
- intel nuc6cays firmwarebefore 0064
- intel nuc6i5syh firmwarebefore 0072
- intel nuc6i7kyk firmwarebefore 0066
- intel nuc7cjyh firmwarebefore 0053
- intel nuc7i3dnhe firmwarebefore 0067
- intel nuc7i5dnke firmwarebefore 0067
- intel nuc7i7dnke firmwarebefore 0067
- intel nuc8i3cysm firmwarebefore 0043
- intel nuc8i7bek firmwarebefore 0077
- intel nuc8i7hnk firmwarebefore 0059
- intel stk2m3w64cc firmwarebefore 0062
- intel stk2mv64cc firmwarebefore 0061
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) NUC(R)
- See Referencesaffected
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-14608Improper buffer restrictions in firmware for Intel(R) NUC(R) may allow an authenticated user to potentially enable escalation of privilege v31Monitor
- CVE-2019-14570Memory corruption in system firmware for Intel(R) NUC may allow a privileged user to potentially enable escalation of privilege, denial of s31Monitor
- CVE-2019-14569Pointer corruption in system firmware for Intel(R) NUC may allow a privileged user to potentially enable escalation of privilege, denial of 31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-14609Dec 16, 2019 · Improper input validation in firmware for Intel(R) NUC(R) may allow a privileged user to potentially enable escalation of privilege via loca26Monitor
- Later →CVE-2019-14611Dec 16, 2019 · Integer overflow in firmware for Intel(R) NUC(R) may allow a privileged user to potentially enable escalation of privilege via local access.26Monitor
- Later →CVE-2019-14612Dec 16, 2019 · Out of bounds write in firmware for Intel(R) NUC(R) may allow a privileged user to potentially enable escalation of privilege via local acce26Monitor
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)
—
CVSS vector
CVSS:3.1/AV:L/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change 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.