AndroidOperating system · Google

CVE-2016-7988

HIGH · 7.5 CVSS v3.0 Published 2016-10-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
On Samsung Galaxy S4 through S7 devices, absence of permissions on the BroadcastReceiver responsible for handling the com.[Samsung].android.intent.action.SET_WIFI intent leads to unsolicited configuration messages being handled by wifi-service.jar within the Android Framework, a subset of SVE-2016-6542.

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

A BroadcastReceiver in Samsung Galaxy S4-S7 devices that handles the com.[Samsung].android.intent.action.SET_WIFI intent lacks proper permission protection, allowing any installed application to send unsolicited WiFi configuration messages directly to the system's wifi-service.jar component without authentication.

MitigationThis is a device firmware vulnerability requiring Samsung to add permission enforcement to the BroadcastReceiver. Users should apply Samsung security updates as they become available.

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:= 4.2.2= 4.3= 4.3.1= 4.4= 4.4.1= 4.4.2= 4.4.3= 4.4.4= 5.0= 5.0.1= 5.0.2= 5.1

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device model
    Check if the device is a Samsung Galaxy S4, S5, S6, or S7 by going to Settings > About Phone > Model Number
    Affected if The model number starts with GT-I9500 (S4), GT-I9505, SM-G900 (S5), SM-G920 (S6), or SM-G930 (S7) series
  2. Check Android version
    Navigate to Settings > About Phone > Android version
    Affected if The Android version is 4.2.2, 4.3, 4.3.1, 4.4 through 4.4.4, or 5.0 through 5.1
  3. Verify Samsung security patch level
    Go to Settings > About Phone > Security patch level (or Settings > Security > Security policy version)
    Affected if The security patch level is earlier than the October 2016 Samsung security update or shows no patch date
  4. Confirm vulnerable BroadcastReceiver presence
    Use a rooted shell or ADB to check if the BroadcastReceiver handling com.samsung.android.intent.action.SET_WIFI exists in the system: `dumpsys package | grep -i 'SET_WIFI'` or inspect the Samsung framework APK
    Affected if A BroadcastReceiver is registered for the SET_WIFI intent without permission requirements
  5. Test intent accessibility (requires technical expertise)
    Use ADB or a test app to send the intent `com.samsung.android.intent.action.SET_WIFI` without any signature or system permissions and observe if it reaches wifi-service.jar
    Affected if The intent is processed without permission errors

The device is affected if it is a Samsung Galaxy S4-S7 running Android 4.2.2-5.1 without the October 2016 or later Samsung security update and the vulnerable SET_WIFI BroadcastReceiver is present without permission enforcement.

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

This is a device firmware vulnerability requiring Samsung to add permission enforcement to the BroadcastReceiver. Users should apply Samsung security updates as they become available.

We can implement and validate the mitigation, then track the permanent fix — typical engagement from $1,950. Get help mitigating

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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