AndroidOperating system · Google

CVE-2017-0706

MEDIUM · 6.8 CVSS v3.0 Published 2017-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
A elevation of privilege vulnerability in the Broadcom wi-fi driver. Product: Android. Versions: Android kernel. Android ID: A-35195787. References: B-RB#120532.

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 confidence

This is an elevation of privilege vulnerability in the Broadcom Wi-Fi driver for Android. The vulnerability exists in the driver code that operates at the kernel level, allowing a malicious application to potentially gain elevated system privileges through the Wi-Fi subsystem. The specific vulnerability mechanism is not detailed in the available description.

MitigationApply the Android security patch level for June 2017 or later, which includes the fix for this Broadcom Wi-Fi driver vulnerability. Users should ensure their devices receive regular security updates from their device manufacturers.

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
AndroidOperating system
Affected:= 7.1.2

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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:P/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. Check Android version
    Go to Settings > About phone (or About device) > Android version. Verify the version is exactly 7.1.2.
    Affected if Android version is 7.1.2
  2. Confirm Broadcom Wi-Fi chipset is present
    Check device specifications or examine kernel module information via terminal: 'ls -la /system/lib/modules/' or check 'getprop ro.wifi.driver' if available. Broadcom Wi-Fi drivers typically appear as files containing 'bcmdhd', 'brcm', or 'broadcom' in the module or driver directory.
    Affected if Device uses a Broadcom Wi-Fi chipset and driver
  3. Verify Wi-Fi driver kernel module
    Run 'lsmod' in a terminal to list loaded kernel modules. Look for modules named 'bcmdhd', 'brcmfmac', 'brcmutil', or similar Broadcom identifiers.
    Affected if Broadcom Wi-Fi kernel module is loaded and the Android version is 7.1.2

A device is affected if it runs Android 7.1.2 and contains a Broadcom Wi-Fi driver/chipset, since this specific version is the only affected Android release listed.

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 the Android security patch level for June 2017 or later, which includes the fix for this Broadcom Wi-Fi driver vulnerability. Users should ensure their devices receive regular security updates from their device manufacturers.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-0706 — 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-2017-0706 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