Skip to content
Fencer Intel
high 8.8

CVE-2013-6271 json

Android 4.0 through 4.3 allows attackers to bypass intended access restrictions and remove device locks via a crafted application that invo…

published 12y ago modified 4mo ago also EUVD-2013-6099

cvss
8.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.0%
EPSS 8.0% chance of exploitation in 30 days, percentile 94%
public exploits
1
Metasploit

Summary

Android 4.0 through 4.3 allows attackers to bypass intended access restrictions and remove device locks via a crafted application that invokes the updateUnlockMethodAndFinish method in the com.android.settings.ChooseLockGeneric class with the PASSWORD_QUALITY_UNSPECIFIED option.

Is CVE-2013-6271 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit post/android/manage/remove_lock)
  2. Published

Exploit prediction

8.03% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit post/android/manage/remove_lock Android Settings Remove Device Locks (4.0-4.3) metasploit post, normal rank, 2013-10-11
  • cureblog.de https://cureblog.de/2013/11/cve-2013-6271-remove-device-locks-from-android-phone/ referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2013/Nov/204 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 8.8 AV:N/AC:M/Au:N/C:C/I:C/A:N

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.