CVE-2017-0792
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 · uneditedA information disclosure vulnerability in the Broadcom wi-fi driver. Product: Android. Versions: Android kernel. Android ID: A-37305578. References: B-V2017052301.
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 confidenceInformation disclosure vulnerability in the Broadcom Wi-Fi driver for Android kernel. Allows unauthorized access to sensitive information through a flaw in the Wi-Fi driver component. The vulnerability enables a local attacker with adjacent network access to potentially retrieve sensitive data from the Wi-Fi driver memory.
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= 7.1.2CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify Android versionGo to Settings > About Phone > Android version (or Settings > System > About Phone > Android version) and note the exact version numberAffected if The device is running Android version 7.1.2 exactly
-
Confirm Broadcom Wi-Fi hardwareCheck device specifications or review Wi-Fi adapter details in Settings > About Phone > Wi-Fi MAC address, or check /system/lib/modules for Broadcom Wi-Fi driver files (often named with 'bcmdhd' or 'bcm' prefixes)Affected if The device uses a Broadcom Wi-Fi chipset and driver
-
Verify Wi-Fi driver is loadedCheck if Wi-Fi is enabled and the driver module is loaded. On Android, you can use a terminal app to run 'lsmod | grep -i bcm' or check /proc/modules for loaded Wi-Fi driver modulesAffected if The Broadcom Wi-Fi driver module is active and loaded into kernel memory
-
Check security patch levelGo to Settings > About Phone > Security patch level (or Settings > System > About Phone > Security update) to see the installed Android security update dateAffected if The device has not received the January 2018 or later Android security patches
A device is affected if it runs Android 7.1.2 with an active Broadcom Wi-Fi driver and lacks the CVE-2017-0792 security patch (January 2018 or later).
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.
From vendor dataApply available Android security patches and update Broadcom Wi-Fi firmware to patched versions. Update affected Android devices to the latest security patch level.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2017-0792 — 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-0792 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