Persistent Phone app crash loop via resource exhaustion
Published Aug 11, 2022 · Updated Aug 3, 2024
Denial of service in the Android 13 Phone app allows local users to trigger a persistent crash loop without user interaction. The public record identifies resource exhaustion in the Phone app but does not disclose the exhausted resource, triggering input, or faulty operation. Execution with ordinary user privileges is required, and exploitation persistently prevents normal Phone app availability without reported confidentiality or integrity impact.
Summary
What happened
Denial of service in the Android 13 Phone app allows local users to trigger a persistent crash loop without user interaction. The public record identifies resource exhaustion in the Phone app but does not disclose the exhausted resource, triggering input, or faulty operation. Execution with ordinary user privileges is required, and exploitation persistently prevents normal Phone app availability without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2022-20260
- Published
- Aug 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
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