Physical app-lock bypass via improper task check
Published Jun 11, 2021 · Updated Aug 3, 2024
Authentication bypass in S Secure on Samsung Mobile Devices P(9.0) allows physically proximate attackers to use a locked app. The app-lock component checks the running task incorrectly, allowing protected application functionality to remain accessible; Samsung has not disclosed the specific code path. Physical access and user interaction are required, and the documented consequence is unauthorized use of the protected app rather than device-wide control.
Summary
What happened
Authentication bypass in S Secure on Samsung Mobile Devices P(9.0) allows physically proximate attackers to use a locked app. The app-lock component checks the running task incorrectly, allowing protected application functionality to remain accessible; Samsung has not disclosed the specific code path. Physical access and user interaction are required, and the documented consequence is unauthorized use of the protected app rather than device-wide control.
The record
- CVE
- CVE-2021-25389
- Published
- Jun 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-287
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2021CVE 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=P(9.0) <SMR MAY-2021 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