CVE-2017-3197 json
GIGABYTE BRIX UEFI firmware fails to securely implement BIOS write protection
published 2018-07-09 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-12323
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.6%
- EPSS 5.6% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
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.
Exploit prediction
5.57% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/CylanceVulnResearch/disclosures/blob/master/CLVA-2017-01-001.md referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/CylanceVulnResearch/disclosures/blob/master/CLVA-2017-01-002.md referenced PoC, tagged "exploit" by a source, unverified
- cylance.com https://www.cylance.com/en_us/blog/gigabyte-brix-systems-vulnerabilities.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- GIGABYTE GB-BSi7H-6500
- GIGABYTE GB-BXi7-5775
Classification
References
-
github.com
/CylanceVulnResearch/disclosures/blob/master/CLVA-2017-01-001.md
exploit, third-party-advisory
-
github.com
/CylanceVulnResearch/disclosures/blob/master/CLVA-2017-01-002.md
exploit, third-party-advisory
-
cylance.com
/en_us/blog/gigabyte-brix-systems-vulnerabilities.html
exploit, third-party-advisory
-
kb.cert.org
/vuls/id/507496
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/97294
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-3197
- NVD CVE-2017-3197
Fencer Vulns 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.