Local privilege escalation via protobuf decode corruption
Published Jun 15, 2022 · Updated Aug 3, 2024
Memory corruption in Android 12L's nanopb library allows local users to elevate privileges by decoding untrusted protobuf files. The public record identifies multiple decoder locations but does not disclose which nanopb functions or unchecked operations corrupt memory. Exploitation requires local low-privileged access, needs no user interaction, and can compromise confidentiality, integrity, and availability.
Summary
What happened
Memory corruption in Android 12L's nanopb library allows local users to elevate privileges by decoding untrusted protobuf files. The public record identifies multiple decoder locations but does not disclose which nanopb functions or unchecked operations corrupt memory. Exploitation requires local low-privileged access, needs no user interaction, and can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2022-20203
- Published
- Jun 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 15, 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-12L
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