CVE-2019-14610 json
Improper access control in firmware for Intel(R) NUC(R) may allow an authenticated user to potentially enable escalation of privilege via l…
published 6y ago modified 4mo ago also EUVD-2019-5771
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Improper access control in firmware for Intel(R) NUC(R) may allow an authenticated user to potentially enable escalation of privilege via local access.
Patch / fix
- intel nuc_8_mainstream_game_kit_firmware 0036
- intel nuc_8_mainstream_game_mini_computer_firmware 0036
- intel nuc8i7bek_firmware 0077
- intel cd1p64gk_firmware 0053
- intel nuc8i3cysm_firmware 0043
- intel nuc8i7hnk_firmware 0059
- intel nuc7i7dnke_firmware 0067
- intel nuc7i5dnke_firmware 0067
- intel nuc7i3dnhe_firmware 0067
- intel stk2mv64cc_firmware 0061
- intel stk2m3w64cc_firmware 0062
- intel nuc6i7kyk_firmware 0066
- intel nuc6i5syh_firmware 0072
- intel nuc7cjyh_firmware 0053
- intel cd1m3128mk_firmware 0058
- intel cd1iv128mk_firmware 0038
- intel nuc6cays_firmware 0064
- intel de3815tybe_firmware 0024
- intel d34010wyb_firmware 0054
Is CVE-2019-14610 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- n/a Intel(R) NUC(R)
References
-
intel.com
/content/www/us/en/security-center/advisory/intel-sa-00323.html
patch, vendor-advisory
Sources
- CVE List CVE-2019-14610
- NVD CVE-2019-14610
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.