CVE-2015-3860 json
packages/Keyguard/res/layout/keyguard_password_view.xml in Lockscreen in Android 5.x before 5.1.1 LMY48M does not restrict the number of ch…
published 11y ago modified 4mo ago also EUVD-2015-3896
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
packages/Keyguard/res/layout/keyguard_password_view.xml in Lockscreen in Android 5.x before 5.1.1 LMY48M does not restrict the number of characters in the passwordEntry input field, which allows physically proximate attackers to bypass intended access restrictions via a long password that triggers a SystemUI crash, aka internal bug 22214934.
Patch / fix
Is CVE-2015-3860 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 FencerExploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- code.google.com https://code.google.com/p/android/issues/detail?id=178139 referenced PoC, tagged "exploit" by a source, unverified
- sites.utexas.edu http://sites.utexas.edu/iso/2015/09/15/android-5-lockscreen-bypass/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
android.googlesource.com
/platform/frameworks/base/+/8fba7e6931245a17215e0e740e78b45f6b66d590
vendor-advisory
-
code.google.com
/p/android/issues/detail?id=178139
exploit
-
sites.utexas.edu
/iso/2015/09/15/android-5-lockscreen-bypass/
exploit
-
groups.google.com
/forum/message/raw?msg=android-security-updates/1M7qbSvACjo/Y7jewiW1AwAJ
mailing-list, vendor-advisory
Sources
- CVE List CVE-2015-3860
- NVD CVE-2015-3860
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.