Buffer Overflow in Broadcom Hardmac Wi Fi Soc Firmware (CVE-2017-6956)
Summary
Vulnerability in Broadcom Hardmac Wi Fi Soc Firmware (CVE-2017-6956). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
On the Broadcom Wi-Fi HardMAC SoC with fbt firmware, a stack buffer overflow occurs when handling an 802.11r (FT) authentication response, leading to remote code execution via a crafted access point that sends a long R0KH-ID field in a Fast BSS Transition Information Element (FT-IE).
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2017-6956 has been found in Broadcom Hardmac Wi Fi Soc Firmware.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Broadcom Hardmac Wi Fi Soc Firmware CVE-2017-6956" on the vendor's site.
CVE-2017-6956 (Broadcom Hardmac Wi Fi Soc Firmware) — CWE-119 / CVSS v3 8.8
Attack vector: adjacent-network / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-119) exists in Broadcom Hardmac Wi Fi Soc Firmware.
Check the vendor advisory for the affected versions of Broadcom Hardmac Wi Fi Soc Firmware.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Broadcom Hardmac Wi Fi Soc Firmware を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory bugs.chromium.org
- advisory googleprojectzero.blogspot.com