Persistent service degradation via zen-rule limit bypass
Published Oct 11, 2022 · Updated Aug 3, 2024
Resource exhaustion in ZenModeHelper in Google Cloud Android 10 through 13 allows local users to cause persistent device performance degradation. addAutomaticZenRule counts rules by individual owner or activity instead of their package, allowing one package to evade the intended rule limit with multiple owners. User-level execution and no interaction are required; exhausting the rule capacity can leave device performance permanently degraded.
Summary
What happened
Resource exhaustion in ZenModeHelper in Google Cloud Android 10 through 13 allows local users to cause persistent device performance degradation. addAutomaticZenRule counts rules by individual owner or activity instead of their package, allowing one package to evade the intended rule limit with multiple owners. User-level execution and no interaction are required; exhausting the rule capacity can leave device performance permanently degraded.
The record
- CVE
- CVE-2022-20425
- Published
- Oct 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-400, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 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-10 Android-11 Android-12 Android-12L 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