Loading vulnerability…
CVE-2022-20474 is a local privilege escalation vulnerability in Android affecting versions 10, 11, 12, 12L, and 13. The flaw is in Parcel.java, specifically in the readLazyValue functionality, where a confused deputy condition can allow arbitrary code to be loaded into the System Settings application. Because the vulnerable code path can cause a more-privileged component to perform unsafe loading on behalf of a less-privileged actor, an attacker may be able to cross privilege boundaries and execute within the context of the targeted privileged app. Exploitation does not require user interaction and, according to the available information, does not require additional execution privileges beyond the attacker's existing local foothold.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (POC) Android application demonstrating exploitation of CVE-2022-20474, a vulnerability in the Android framework's Bundle deserialization logic. The exploit leverages the ability to craft a Bundle containing a LazyValue with a negative length, which can cause the deserialization process to misbehave, potentially allowing a self-changing Bundle and bypassing security checks. The main exploit logic is implemented in 'app/src/main/java/com/cxxsheng/cve_2022_20474/MainActivity.java', where the 'make' function constructs a malicious Bundle and 'simulateIPCBundle' mimics the IPC process to demonstrate the effect. The repository includes standard Android project files, build scripts, and resources, but the core exploit is in the Java code. No network endpoints or external IPs are present; the attack vector is local, requiring execution on a vulnerable Android device. The exploit does not provide a weaponized payload but serves as a technical demonstration of the vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.