Physical PIN bypass via editable backup settings
Published Jan 31, 2020 · Updated Aug 6, 2024
Authentication bypass in LastPass Android before 2.5.1 allows physically proximate attackers to access stored credentials via ADB backups. Android backup data stores PIN and wipe settings in LPandroid.xml, which an attacker can edit and restore to disable PIN checks and auto-wipe. Physical device access and USB debugging are required; the result is disclosure of cached credentials and possible account takeover.
Summary
What happened
Authentication bypass in LastPass Android before 2.5.1 allows physically proximate attackers to access stored credentials via ADB backups. Android backup data stores PIN and wipe settings in LPandroid.xml, which an attacker can edit and restore to disable PIN checks and auto-wipe. Physical device access and USB debugging are required; the result is disclosure of cached credentials and possible account takeover.
The record
- CVE
- CVE-2013-5113
- Published
- Jan 31, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-522, T1555
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo