Physical privilege escalation via factory reset permission bypass
Published Aug 11, 2022 · Updated Aug 3, 2024
Permissions bypass in Android 13 Settings allows physically proximate attackers to obtain elevated privileges through factory reset controls. Google has not published the affected Settings function or how it fails to enforce factory reset permission checks. Physical access is required; no prior execution privileges or user interaction is needed, and the documented consequence is local privilege escalation.
Summary
What happened
Permissions bypass in Android 13 Settings allows physically proximate attackers to obtain elevated privileges through factory reset controls. Google has not published the affected Settings function or how it fails to enforce factory reset permission checks. Physical access is required; no prior execution privileges or user interaction is needed, and the documented consequence is local privilege escalation.
The record
- CVE
- CVE-2022-20265
- Published
- Aug 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- T1404
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 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=Android-13
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