Gigabyte GB-BSi7H-6500/GB-BXi7-5775 BIOSWE/BLE/SMM_BWP/PRx input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Gigabyte GB-BSi7H-6500 and GB-BXi7-5775. It has been classified as critical. This affects an unknown function of the component BIOSWE/BLE/SMM_BWP/PRx. Performing a manipulation results in input validation. This vulnerability is cataloged as CVE-2017-3197. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in Gigabyte GB-BSi7H-6500 and GB-BXi7-5775 (unknown version). This affects an unknown code block of the component BIOSWE/BLE/SMM_BWP/PRx. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
GIGABYTE BRIX UEFI firmware for the GB-BSi7H-6500 (version F6) and GB-BXi7-5775 (version F2) platforms does not securely implement BIOSWE, BLE, SMM_BWP, and PRx features. As a result, the BIOS is not protected from arbitrary write access and may permit modifications to the SPI flash.
The bug was discovered 03/31/2017. The weakness was shared 07/09/2018 by Alex Matrosov with Cylance as confirmed advisory (CERT.org). The advisory is shared at kb.cert.org. This vulnerability is uniquely identified as CVE-2017-3197 since 12/05/2016. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 465 days. During that time the estimated underground price was around $0-$5k.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 97294†). The entry VDB-120910 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
12/05/2016 🔍03/31/2017 🔍
03/31/2017 🔍
07/09/2018 🔍
07/09/2018 🔍
07/10/2018 🔍
12/27/2024 🔍
Sources
Advisory: kb.cert.orgResearcher: Alex Matrosov
Organization: Cylance
Status: Confirmed
CVE: CVE-2017-3197 (🔍)
GCVE (CVE): GCVE-0-2017-3197
GCVE (VulDB): GCVE-100-120909
CERT: 🔍
SecurityFocus: 97294 - Multiple GIGABYTE Products VU#507496 Multiple Security Bypass Vulnerabilities
See also: 🔍
Entry
Created: 07/10/2018 09:49Updated: 12/27/2024 13:35
Changes: 07/10/2018 09:49 (64), 03/03/2020 10:59 (1), 12/27/2024 13:35 (17)
Complete: 🔍
Cache ID: 216:54D: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.