Lockscreen attempt reset via bootloader fault injection
Published Dec 31, 2024 · Updated Dec 31, 2024
Protection mechanism failure in the Samsung Mobile Devices bootloader before SMR Oct-2024 Release 1 lets physical attackers reset lockscreen attempts. The bootloader fails to validate the lockscreen failure counter against hardware fault injection, so injected faults reset the recorded count. Physical access and user interaction are required; resetting the counter permits additional lockscreen guesses without directly unlocking the device.
Summary
What happened
Protection mechanism failure in the Samsung Mobile Devices bootloader before SMR Oct-2024 Release 1 lets physical attackers reset lockscreen attempts. The bootloader fails to validate the lockscreen failure counter against hardware fault injection, so injected faults reset the recorded count. Physical access and user interaction are required; resetting the counter permits additional lockscreen guesses without directly unlocking the device.
The record
- CVE
- CVE-2024-49422
- Published
- Dec 31, 2024
- Updated
- Dec 31, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-693, T1110
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 31, 2024CVE publishedPublication date reported by the CVE source.
- Dec 31, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
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