# CVE-2017-3197: GIGABYTE BRIX UEFI firmware fails to securely implement BIOS write protection

> Attackers can bypass BIOS write protection to modify SPI flash, enabling persistent code execution and privilege escalation on GIGABYTE BRIX devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r83h-qmfh-pxvf

## What is CVE-2017-3197?

CVE-2017-3197 is a critical vulnerability in GIGABYTE GB-BSi7H-6500, published on 9 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation), CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2017-3197?

It affects 2 products.


Products: Gigabyte Gb-Bsi7h-6500 Firmware, Gigabyte Gb-Bxi7-5775 Firmware.

## How do I fix CVE-2017-3197?

No fix has been published for CVE-2017-3197 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-3197 being exploited?

There is no known exploitation of CVE-2017-3197 in the wild and no public exploit code.

## Other vulnerabilities in GIGABYTE GB-BSi7H-6500

- [CVE-2017-3198](https://insights.sbomify.com/CVE-2017-3198/): GIGABYTE BRIX UEFI firmware is not cryptographically signed (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3197 and fix it if it is affected.

What it is: CVE-2017-3197 is a critical vulnerability in GIGABYTE GB-BSi7H-6500, published on 9 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3197 in the wild and no public exploit code.

Affected product: GIGABYTE GB-BSi7H-6500. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-3197/ (Markdown: https://insights.sbomify.com/CVE-2017-3197/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3197
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3197
- OSV: https://osv.dev/vulnerability/CVE-2017-3197

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-3197/
Summaries are generated and may contain mistakes; the official description above is the record.