As reported by The Hacker News, a critical unpatched vulnerability in Broadcom's Wi-Fi Protected Setup (WPS) implementation allows attackers within radio range to execute arbitrary code as root on affected routers — without knowing the Wi-Fi password or completing any pairing step. Security researcher Quentin Kaiser demonstrated the exploit on October 16 against ISP-issued gateways from three Belgian providers, including extracting a Wi-Fi PSK over the air and opening a reverse shell carried entirely over Wi-Fi frames. No CVE has been assigned, and no patch is available for many affected devices.

Security Impact: As reported by The Hacker News, a critical unpatched vulnerability in Broadcom's Wi-Fi Protected Setup (WPS) implementation allows attackers within radio range to execute arbitrary code as root on affected routers — without knowing the Wi-Fi password or completing any pairing step.

This is not a typical network vulnerability. The attack requires only physical proximity to a vulnerable device — no credentials, no prior access, and no network-side interaction. By exploiting a memory corruption bug in Broadcom's fragmented WPS message reassembly logic, Kaiser built both an information disclosure primitive (reading router memory) and a code execution primitive. The implications for ISP-issued consumer gateways, which are rarely updated and often sit unmonitored in homes and small offices for years, are severe.

Vulnerability Details

AttributeDetails
ComponentBroadcom Wi-Fi Protected Setup (WPS) implementation
Root CauseMishandled reassembly of fragmented WPS setup messages leading to memory corruption
ImpactArbitrary code execution as root; memory disclosure (PSK extraction)
Attack VectorWi-Fi radio range — no credentials, no pairing required
CVENot yet assigned
CVSS / SeverityCritical (unofficial — remote pre-auth root code execution)
Patch StatusNo fix deployed. Broadcom shipped incomplete fix in 2018; older chipsets are a permanent "forever day"
Active ExploitationNone reported in the wild (proof-of-concept only)

Affected Chipsets

  • eCos-based (likely unpatchable): BCM3380, BCM3383, BCM33834
  • Linux-based (potentially patchable): BCM3390, BCM65xx, BCM68xx

Confirmed Exploitable ISP Gateways

  • Orange Belgium — Askey TCG3000 (PSK extracted over the air)
  • Proximus — Sagemcom BBOX3V+ (reverse shell over Wi-Fi frames)
  • VOO — confirmed vulnerable
  • Telenet — untested, likely affected

Why This Matters

The vulnerability's reach is the critical concern. Broadcom's WPS code is embedded in routers and access points from dozens of vendors worldwide — Cisco small-business APs, Huawei, ARRIS, Sagemcom, Askey, and many more. Kaiser estimates millions of affected devices. The flaw has existed since at least 2010, meaning an entire generation of Broadcom-based gateways has shipped with this defect for over 15 years.

The concept of a

forever day
— a vulnerability the vendor will never patch — is particularly relevant here. Older eCos-based chipsets have no viable fix path. These devices will remain exploitable until they are decommissioned. For ISPs that have deployed these gateways at scale, there is no software remediation available; the only answer is hardware replacement.

For enterprises, the risk extends to any Broadcom-based small-business access points still in service, particularly in branch offices or IoT deployments where physical access controls to the wireless perimeter are weak.

Shield53 Recommendations

Immediate Actions

Shield53 Recommendations
Inventory and identify: Audit all wireless infrastructure for Broadcom chipsets listed above. Cross-reference against Kaiser's published device list for likely-affected models.
Disable WPS: Turn off Wi-Fi Protected Setup on all routers and access points immediately. This closes the vulnerable attack surface even if the underlying firmware remains unpatched.
Plan hardware replacement: For eCos-based devices (BCM3380/3383/33834), initiate procurement of replacement gateways. No patch will come. Prioritize ISP-issued consumer equipment in production environments.
Engage ISPs: If your organization relies on ISP-managed gateways, formally request firmware updates or hardware swaps. Escalate to account management if needed.
Monitor for exploitation: Watch for anomalous WPS traffic, unexpected deauth or beacon frames, and unusual Wi-Fi frame sizes that could indicate memory corruption exploitation attempts. Deploy wireless IDS/IPS where feasible.
Segment networks: Ensure routers and IoT devices sit on isolated VLANs. A compromised gateway should not provide a pivot point into sensitive internal segments.

Strategic Actions

  • Eliminate Broadcom eCos-based wireless equipment from your approved hardware standards.
  • Add WPS disablement to your baseline router/AP hardening configuration templates.
  • Incorporate firmware EOL and "forever day" risk into vendor risk assessments for all network equipment procurement.

This disclosure is a reminder that proximity-based wireless attacks remain a potent and underappreciated threat vector. Defenders who focus exclusively on internet-facing perimeter controls are blind to an attacker parked outside with a laptop and a Wi-Fi adapter. The absence of a CVE and the fragmented vendor ecosystem mean there will be no single advisory to track — organizations must take ownership of identifying and remediating this risk themselves.