Security readout for executives and security teams
Some GIGABYTE BRIX systems accepted firmware updates without cryptographic verification, and updates were delivered over HTTP. That means a tampered firmware image could be installed without detection if an attacker can interfere with the update path. Firmware compromise can persist below the operating system, so affected devices deserve focused inventory and vendor-guidance review. Exposure appears limited to the listed GIGABYTE BRIX models and firmware versions in the source bundle. Organizations are most exposed where these devices remain deployed and firmware updates can be fetched or applied over untrusted network paths. Prioritize inventory and remediation planning where affected BRIX systems support sensitive operations. The risk is not broad internet exposure, but a successful firmware compromise could be persistent and difficult to detect. Mitigation focus: Inventory for GB-BSi7H-6500 F6 and GB-BXi7-5775 F2 devices.; Check GIGABYTE and CERT guidance for current firmware or replacement recommendations.; Avoid firmware updates over untrusted networks or unauthenticated download paths..
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-345: 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-3198 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
- 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.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.