Security readout for executives and security teams
This issue means specific GIGABYTE BRIX systems may not protect their firmware from unauthorized writes. If an attacker already reaches the level needed to write firmware, they could alter SPI flash and potentially persist below the operating system. Exposure is limited to the two named GIGABYTE BRIX platforms and firmware versions in the source bundle. Organizations with these devices in kiosks, labs, industrial use, or unmanaged endpoint fleets should verify model and firmware inventory. Treat confirmed affected systems as high-priority remediation candidates, especially where they support sensitive operations. The issue is narrow in product scope but high impact if abused. Mitigation focus: Inventory BRIX systems and confirm exact model and UEFI firmware version.; Check GIGABYTE and CERT guidance for supported firmware updates or mitigations.; Prioritize replacement or isolation if affected firmware cannot be remediated..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2017-3197 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/CylanceVulnResearch/disclosures/blob/master/CLVA-2017-01-001.mdCVE reference · x_refsource_MISC
- https://github.com/CylanceVulnResearch/disclosures/blob/master/CLVA-2017-01-002.mdCVE reference · x_refsource_MISC
- VU#507496CVE reference · third-party-advisory, x_refsource_CERT-VN
- https://www.cylance.com/en_us/blog/gigabyte-brix-systems-vulnerabilities.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.