Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Showing posts with label Broadcom.. Show all posts

Millions of Routers Running Broadcom Wi-Fi Chips Have an Unpatched Flaw That Hands Attackers Root Access Over the Air

 




A security researcher has demonstrated working exploits against a class of Wi-Fi gateways running Broadcom chips, showing that an attacker within radio range can gain root-level code execution on the device without knowing the Wi-Fi password or completing any kind of pairing process. As of this writing, no patch has been deployed to affected routers, and no CVE identifier has been assigned.

Quentin Kaiser published his findings on October 16, 2026, after a disclosure process that effectively went nowhere. The vulnerability sits inside Broadcom's own implementation of Wi-Fi Protected Setup, the handshake protocol designed to simplify connecting new devices to a network. Kaiser found that the code mishandles the reassembly of fragmented WPS messages. By sending carefully crafted fragments, an attacker can corrupt the device's memory and redirect execution, all through the air, from a position outside the building.


Two Working Exploits, Two Different Outcomes

Kaiser demonstrated the attack against two Belgian ISP-supplied gateways. On an Orange Belgium device, an Askey TCG3000, the exploit read the Wi-Fi pre-shared key directly from stored settings and transmitted it back to the attacker, effectively handing over the network password. On a Proximus gateway, the Sagemcom BBOX3V+, the exploit did something more severe: it opened a reverse shell transported entirely over Wi-Fi frames, without requiring the attacker to have an external server or any prior foothold on the network.

Both attacks required no credentials and no interaction from anyone inside the network. Distance helps the attacker, not the defender.


The Code Is Old, and So Is Broadcom's Awareness

The vulnerable code traces back to at least 2010. Broadcom issued a partial fix in 2018 and simultaneously told downstream customers to migrate to the hostapd Wi-Fi software package instead of relying on Broadcom's own WPS implementation. That guidance went unheeded across a large portion of the device ecosystem, and the underlying flaw was never fully resolved.

Kaiser says Broadcom was informed about the issue again through his disclosure process and declined to assign a CVE or comment publicly. CERT/CC, which typically coordinates vulnerability disclosures between researchers and vendors, closed his case the day it was opened, citing the fact that Broadcom holds its own CVE numbering authority.

The result is a vulnerability without an identifier, without a patch, and without any official acknowledgment from the company whose code is responsible.


Which Hardware Is Affected

Kaiser sorted the affected chips into two groups. Older eCos-based chips, the BCM3380, BCM3383, and BCM33834, cannot receive a practical fix given their architecture. He described these as a "forever day," meaning a vulnerability that will remain open for the functional life of the hardware. Newer Linux-based chips, including the BCM3390, BCM65xx, and BCM68xx series, are technically fixable if device makers choose to replace the WPS software stack.

Among confirmed deployments in Belgium, Proximus, Orange Belgium, and VOO gateways are affected. Kaiser was unable to test Telenet devices but considers them potentially in scope. His broader analysis, which involved automated firmware scanning, identified vulnerable code across Cisco small-business access points, Huawei gear, and ARRIS routers, among others. He estimates the total number of affected devices runs into the millions globally, though some entries in his published list are flagged as "likely vulnerable" rather than confirmed.


Detection Tools, but No Mitigation

For organizations trying to assess their exposure, Kaiser published YARA detection rules and a scanning script on GitHub at github.com/qkaiser/broadcom-wps. Both are intended as triage tools to identify firmware containing the vulnerable code. He notes that patched devices may still trigger the YARA rules, so a positive result requires additional verification rather than automatic remediation.

For devices that fall into the "forever day" category, the practical answer is replacement.


Why Proximity Attacks Are Getting More Attention

The threat model here matters beyond the technical details. Kaiser noted that this vulnerability is particularly useful to attackers who can position themselves in physical range of a target rather than approaching through the internet. That scenario is no longer theoretical.

In November 2024, Volexity documented how a Russian state-sponsored group, tracked as GruesomeLarch and linked to APT28, compromised organizations near a high-value target in Washington, D.C., and then used dual-homed systems inside those neighboring buildings to connect to the actual target's corporate Wi-Fi. The attacker never needed to be in the same room or even the same building. They just needed a wireless network with weak enough controls to reach from the street.

A flaw that lets anyone within radio range become root on the router, without a password, without a handshake, fits neatly into that playbook. The attack surface is wherever the signal reaches.



Broadcom WiFi Chipset Driver Defect Takes Its Toll On OSs, IoTs, Phones and Other Devices.




Reportedly, the flaws in the Broadcom WiFi chipset drivers are causing a lot of trouble for phones and operating systems that are exposed to it.


This means, attackers could be allowed to execute arbitrary code and initiate DOS. (Denial of Service)

As reported by an intern of a reputed lab, the Broadcom drivers and the open source “brcmfmac” driver possess several vulnerabilities.

As it turns out, the Broadcom drivers are susceptible to “two heap buffer overflows.” Whereas, the ‘brcmfmac’ drivers are susceptible to frame validation bypass as well as heap buffer overflow.

Per the Common Weakness Enumeration database, the heap buffer overflows could cause the software to run in an infinite loop, system crashes, along with execution of arbitrary code.


These above activities are evidently beyond the security policies and security services.

The aforementioned Broadcom WiFi chips are insidiously used by almost everyone without their knowing it. From a laptop through the IoT devices to the smart TVs all the devices have these chip drivers.


As these chips are enormously prevalent, they comprise of an even more enormous target range. Any simple vulnerability or flaw found in them could be a matter of serious risk.

The Broadcom WiFi chipset drivers could be easily exploited by the unauthenticated attackers by way of sending malicious “WiFi packets”.

These packets would later on help in initiating the arbitrary code execution. All the attacks would simply lead to Denial of Service.

In the list of the risks that stand to vulnerable devices, Denial of Service attacks and arbitrary code execution are on the top. These flaws were found also in Linux kernel and the firmware of Broadcom chips.

According to the source note, the four brcmfmac and Broadcom wl drivers vulnerability is of the sort, CVE-2019-8564, CVE-2019-9500, CVE-2019-9501, CVE-2019-9502, CVE-2019-9503.

·       CVE-2019-9503: When the driver receives the firmware event frame from the remote source, it gets discarded and isn’t processed. When the same is done from the host the appropriate handler is called. This validation could be bypassed if the bus used is a USB.

·       CVE-2019-9500: A malicious event frame could be constructed to trigger a heap buffer overflow.



·       CVE-2019-9501: The vendor is supplied with the information with data larger than 32 bytes and  a heap buffer overflow is triggered in “wlc_wpa_sup_eapol”

·       CVE-2019-9502: when the vendor information data length is larger than 164 bytes a heap buffer overflow is triggered in “wlc_wpa_plumb_gtk”

If the wl driver’s used with SoftMAC chipsets the vulnerabilities are triggered in the host’s kernel whereas, when used with FullMAC chipset, they are triggered in chipset’s firmware.

There are approximately over 160 vendors that stand vulnerable to Broadcom WiFi chipsets within their devices.

Two of Broadcom’s vulnerabilities were patched which were found in the open source brcmfmac Linux kernel.

CVE-2019-8564 vulnerability had been patched by Apple as a part of their security update, a day before the developer revealed the vulnerabilities.