Improper input validation for some Intel NUC BIOS firmware before version JY0070 may allow a…
CVE-2023-28738 is a high-severity improper input validation vulnerability in Intel NUC BIOS firmware, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version JY0070 as the first without the flaw, so updating Intel NUC BIOS firmware to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.16% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Intel NUC BIOS firmware to JY0070 or a later version.
- Read the advisory on intel.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Intel NUC BIOS firmware | Intel NUC BIOS firmware | before version JY0070; before JY0070 | JY0070 |
| Intel | Nuc 7 Essential Nuc7cjysamn Firmware | jyglkcpx.0071 | Not stated |
| Intel | Nuc Kit Nuc7cjyhn Firmware | jyglkcpx.0071 | Not stated |
| Intel | Nuc Kit Nuc7pjyhn Firmware | jyglkcpx.0071 | Not stated |
| Intel | Nuc Kit Nuc7pjyh Firmware | jyglkcpx.0071 | Not stated |
| Intel | Nuc Kit Nuc7cjysal Firmware | jyglkcpx.0071 | Not stated |
| Intel | Nuc Kit Nuc7cjyh Firmware | jyglkcpx.0071 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (intel.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
Improper input validation for some Intel NUC BIOS firmware before version JY0070 may allow a privileged user to potentially enable escalation of privilege via local access.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Intel NUC BIOS firmware
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Recent Improper Input Validation vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 7.1 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.5 High severity
Spotted an error? Tell us.