Router ManagerApplication · Synology

CVE-2019-9502

HIGH · 8.8 CVSS v3.1 Published 2020-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Broadcom wl WiFi driver is vulnerable to a heap buffer overflow. If the vendor information element data length is larger than 164 bytes, a heap buffer overflow is triggered in wlc_wpa_plumb_gtk. 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap buffer overflow in Broadcom wl WiFi driver's wlc_wpa_plumb_gtk function, triggered when vendor information element data length exceeds 164 bytes. Remote unauthenticated attackers can exploit via specially-crafted WiFi packets, potentially achieving arbitrary code execution or causing denial-of-service.

MitigationApply vendor-supplied firmware/driver patch for Broadcom wl; if unavailable, disable WiFi or implement network-level filtering to block malformed vendor information elements.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Router ManagerApplication
Affected:= 1.2
Bcm4339 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Broadcom wl WiFi driver usage
    Check system information or network adapter details to determine if the device uses the Broadcom wl driver for WiFi connectivity
    Affected if The system uses the Broadcom wl driver for WiFi operations
  2. Check for Broadcom Bcm4339 chipset
    Inspect network hardware or WiFi adapter specifications to identify the chipset model; on Linux, 'lspci' or 'lsusb' may list wireless adapters, or check device datasheets
    Affected if The WiFi hardware is based on the Broadcom Bcm4339 chipset
  3. Verify Synology Router Manager version
    Access Synology Router Manager web interface or check system version via CLI if available; look for version 1.2 specifically
    Affected if Synology Router Manager version 1.2 is installed
  4. Confirm WiFi is enabled
    Check wireless interface status via 'iwconfig' or similar tool, or verify in router web interface that WiFi radio is active
    Affected if WiFi is currently enabled and broadcasting
  5. Review system logs for WiFi driver anomalies
    Examine kernel logs (dmesg) or system logs for crash entries, memory corruption indicators, or unexpected reboots potentially linked to the WiFi driver
    Affected if Logs show crashes or instability in the WiFi driver component since the vulnerability publication date

You are affected if your system uses the Broadcom wl driver with Bcm4339 hardware, runs Synology Router Manager 1.2, and has WiFi enabled, making it susceptible to the 164-byte vendor IE overflow.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware/driver patch for Broadcom wl; if unavailable, disable WiFi or implement network-level filtering to block malformed vendor information elements.

Fix this in Router Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-9502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-9502 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data