{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-3197 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-3197 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2017-3197 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2017-3197 in the wild and no public exploit code.\n\nAffected product: GIGABYTE GB-BSi7H-6500. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-3197/ (Markdown: https://insights.sbomify.com/CVE-2017-3197/index.md)","id":"CVE-2017-3197","markdown":"https://insights.sbomify.com/CVE-2017-3197/index.md","name":"CVE-2017-3197","record":{"aliases":["GHSA-r83h-qmfh-pxvf"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"GIGABYTE BRIX firmware","requires_auth":"none","summary":"Attackers can bypass BIOS write protection to modify SPI flash, enabling persistent code execution and privilege escalation on GIGABYTE BRIX devices.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"gb-bsi7h-6500_firmware","vendor":"gigabyte"},{"product":"gb-bxi7-5775_firmware","vendor":"gigabyte"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-693","name":"Protection Mechanism Failure"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"GIGABYTE BRIX UEFI firmware fails to securely implement BIOS write protection","id":"CVE-2017-3197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":5,"next":{"headline":"GIGABYTE BRIX UEFI firmware is not cryptographically signed","id":"CVE-2017-3198"},"packages":[],"prev":{"headline":"Memory corruption in ASUS PCE-AC56 WLAN Card Utilities","id":"CVE-2017-3196"},"products":["GB-BSi7H-6500","GB-BXi7-5775"],"published":"2018-07-09","related":[{"cvss_score":9.8,"headline":"GIGABYTE BRIX UEFI firmware is not cryptographically signed","id":"CVE-2017-3198","kev_date_added":null,"published":"2018-07-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["GIGABYTE"]},"summary":"Attackers can bypass BIOS write protection to modify SPI flash, enabling persistent code execution and privilege escalation on GIGABYTE BRIX devices.","url":"https://insights.sbomify.com/CVE-2017-3197/"}