Root-of-trust alteration via mutable StrongBox state
Published May 3, 2022 · Updated Aug 3, 2024
Improper state maintenance in StrongBox on Samsung Mobile Devices before Galaxy S22 allows local users to alter the Android root of trust. StrongBox fails to lock the Android root-of-trust state after its first boot initialization, permitting later changes during the device boot cycle. Exploitation requires prior compromise and control of the trusted execution environment, and the bounded consequence is loss of Android root-of-trust integrity.
Summary
What happened
Improper state maintenance in StrongBox on Samsung Mobile Devices before Galaxy S22 allows local users to alter the Android root of trust. StrongBox fails to lock the Android root-of-trust state after its first boot initialization, permitting later changes during the device boot cycle. Exploitation requires prior compromise and control of the trusted execution environment, and the bounded consequence is loss of Android root-of-trust integrity.
The record
- CVE
- CVE-2022-28793
- Published
- May 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-754, T1553
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 3, 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=- <Galaxy S22
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