Screen-lock brute force via faulty failure counting
Published Mar 8, 2022 · Updated Aug 3, 2024
Improper fingerprint-attempt limiting in Samsung Mobile Devices before SMR Mar-2022 Release 1 allows physical attackers to brute-force screen locks. The fingerprint matching algorithm's failure counter does not sufficiently limit repeated authentication attempts. Exploitation requires physical access to a selected Android 11 or 12 device and can expose data protected by the screen lock without altering it or interrupting service.
Summary
What happened
Improper fingerprint-attempt limiting in Samsung Mobile Devices before SMR Mar-2022 Release 1 allows physical attackers to brute-force screen locks. The fingerprint matching algorithm's failure counter does not sufficiently limit repeated authentication attempts. Exploitation requires physical access to a selected Android 11 or 12 device and can expose data protected by the screen lock without altering it or interrupting service.
The record
- CVE
- CVE-2022-25820
- Published
- Mar 8, 2022
- Updated
- Aug 3, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-307, T1110
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 8, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Select R(11), S(12) devices <SMR Mar-2022 Release 1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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