Intel NUC7i3BNK/NUC7i3BNH/NUC7i5BNK/NUC7i5BNH/NUC7i7BNH up to BN0049 BIOS Recovery access control

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $5k-$25k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Intel NUC7i3BNK, NUC7i3BNH, NUC7i5BNK, NUC7i5BNH and NUC7i7BNH up to BN0049. The affected element is an unknown function of the component BIOS Recovery. Performing a manipulation results in access control. This vulnerability is known as CVE-2017-5701. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability classified as critical has been found in Intel NUC7i3BNK, NUC7i3BNH, NUC7i5BNK, NUC7i5BNH and NUC7i7BNH up to BN0049. This affects an unknown code of the component BIOS Recovery. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Insecure platform configuration in system firmware for Intel NUC7i3BNK, NUC7i3BNH, NUC7i5BNK, NUC7i5BNH, NUC7i7BNH versions BN0049 and below allows an attacker with physical presence to run arbitrary code via unauthorized firmware modification during BIOS Recovery.
The bug was discovered 10/06/2017. The weakness was published 10/11/2017 (Website). The advisory is shared at security-center.intel.com. This vulnerability is uniquely identified as CVE-2017-5701 since 02/01/2017. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/16/2021). MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 101257†). Similar entries are available at VDB-107684, VDB-107686 and VDB-107687. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.intel.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.4
VulDB Temp Score: 7.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/01/2017 🔍10/06/2017 🔍
10/06/2017 🔍
10/10/2017 🔍
10/11/2017 🔍
10/11/2017 🔍
01/16/2021 🔍
Sources
Vendor: intel.comAdvisory: security-center.intel.com
Researcher: Nikolaj Schlej.
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-5701 (🔍)
GCVE (CVE): GCVE-0-2017-5701
GCVE (VulDB): GCVE-100-107685
SecurityFocus: 101257 - Intel SPI Write Protection CVE-2017-5701 Local Security Bypass Vulnerability
See also: 🔍
Entry
Created: 10/11/2017 10:34Updated: 01/16/2021 08:26
Changes: 10/11/2017 10:34 (59), 11/23/2019 15:23 (4), 01/16/2021 08:26 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.