CVE-2017-0824
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 · uneditedAn elevation of privilege vulnerability in the Broadcom wifi driver. Product: Android. Versions: Android kernel. Android ID: A-37622847. References: B-V2017063001.
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 · moderate confidenceA critical elevation of privilege vulnerability in the Broadcom WiFi driver within the Android kernel allows a local attacker to gain higher privileges. This is a kernel-level driver flaw in Android devices using Broadcom WiFi chipsets.
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<= 8.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check the Android versionGo to Settings > About Phone (or About Device) > Android version. Alternatively, run 'getprop ro.build.version.release' via ADB shell.Affected if The Android version is 8.0 or lower (including 7.x, 6.x, 5.x, etc.)
-
Identify the WiFi chipset vendorCheck the device specifications or use ADB to run 'getprop ro.wifi.interface' and examine kernel modules with 'ls /proc/modules | grep -i wifi' or check '/sys/class/net/wlan0/device' for vendor information.Affected if The device uses a Broadcom (bcmdhd, wl, brcmfmac, or similar) WiFi chipset module.
-
Verify the Broadcom WiFi driver is loadedRun 'lsmod' via ADB shell or check /proc/modules to confirm the Broadcom wireless driver module is actively loaded.Affected if A Broadcom WiFi kernel module (such as bcmdhd, wl, or brcmfmac) is loaded and active.
If the device runs Android 8.0 or lower AND uses a Broadcom WiFi chipset with the vulnerable driver loaded, the environment is affected by CVE-2017-0824.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply the Android security patch released for this vulnerability (refer to the Android security bulletin). Users should ensure their devices receive the latest system and kernel updates from their device manufacturers.
Android security patch level June 2017 or later (or upgrade to Android 8.1/9/10+ with current security patches)
- Check the current Android security patch level on the device in Settings > About Phone > Security Patch Level
- If the patch level is earlier than June 2017, apply the latest available Android security update from your device manufacturer
- For devices that cannot receive the June 2017 or later security patch, consider upgrading to a device that receives regular security updates
- Alternatively, if the device is rooted, ensure the Broadcom wifi driver is not loaded or replace with a patched driver (not recommended as primary mitigation)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0824 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-0824 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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