CVE-2016-0813
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 · uneditedpackages/SystemUI/src/com/android/systemui/recents/AlternateRecentsComponent.java in Setup Wizard in Android 5.1.x before 5.1.1 LMY49G and 6.x before 2016-02-01 does not properly check for device provisioning, which allows physically proximate attackers to bypass the Factory Reset Protection protection mechanism and delete data via unspecified vectors, aka internal bug 25476219.
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 confidenceThis vulnerability in Android's Setup Wizard (AlternateRecentsComponent.java) fails to properly validate device provisioning status before allowing certain operations. This allows a physically proximate attacker with device access to bypass Factory Reset Protection (FRP) and delete data, exploiting the lack of a provisioning check in the recents component.
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= 5.1= 5.1.0= 5.1.1= 6.0= 6.0.1CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:N/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 Android OS versionGo to Settings > About Phone > Android version. Compare the displayed version to the affected versions: 5.1, 5.1.0, 5.1.1, 6.0, or 6.0.1.Affected if The device is running Android version 5.1, 5.1.0, 5.1.1, 6.0, or 6.0.1.
-
Check if device provisioning is incompleteAfter a factory reset, attempt to access the recents screen (recent apps) by pressing the recents button. If the device has completed Setup Wizard and FRP provisioning, this should be restricted.Affected if The recents screen is accessible immediately after a factory reset before completing the Setup Wizard, indicating the device is in an unprovisioned state.
-
Verify FRP bypass riskAfter a factory reset, observe whether the AlternateRecentsComponent allows access to settings or data deletion options without requiring device owner authentication.Affected if Data deletion options or settings are accessible without completing device provisioning, indicating the vulnerability may be present.
-
Confirm security patch levelGo to Settings > About Phone > Security patch level. Check if the patch level is earlier than February 2016 for Android 6.x, or earlier than LMY49G for Android 5.1.x.Affected if The security patch level is earlier than February 2016 for Android 6.x, or earlier than LMY49G for Android 5.1.x.
The device is affected if it runs Android 5.1 through 6.0.1 and has not received the February 2016 security patch (for 6.x) or LMY49G update (for 5.1.x), particularly when the device is in an unprovisioned state after factory reset.
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 dataUpdate affected Android devices to version 5.1.1 LMY49G or later for 5.1.x, or the February 2016 security patch level or later for 6.x to receive the fix.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0813 — 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-2016-0813 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