Loading vulnerability…
An integer overflow exists in the native_handle_create function in libcutils/native_handle.c in Android versions prior to 5.1.1 LMY48M. The vulnerability allows an attacker to trigger a heap memory corruption in the Binder subsystem by passing crafted parameters to native_handle_create, potentially via a malicious application. This can result in privilege escalation or denial of service.
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 multi-stage local privilege escalation exploit targeting Android 5.0 (LRX21O), specifically tested on Nexus 5. The exploit is divided into several components: - The 'mediaserver' folder contains code to inject into the mediaserver process from a normal application context, exploiting binder calls and manipulating system services. - The 'surfaceflinger' folder contains code to further escalate privileges by injecting into the surfaceflinger process, after gaining access via mediaserver. - The 'systemserver' folder contains code to inject into the system_server process, achieving the highest privilege after compromising surfaceflinger. - The 'bbshell' folder provides a mechanism to inject a busybox shell into mediaserver, allowing arbitrary command execution. The exploit chain involves manipulating Android's binder IPC mechanism, exploiting service manager interfaces, and performing code injection via shared memory and ELF manipulation. The code is highly tailored to the target device and Android version, with many hardcoded addresses and paths. The exploit uses several fingerprintable file paths (e.g., /data/local/tmp/bbshell, /data/local/tmp/libexpsur.so, /data/system/tmp/libinject.so) and interacts with system binaries and libraries (e.g., /system/lib/libui.so, /proc/.../maps). The overall purpose is to demonstrate a full privilege escalation chain from a normal app context to system_server, leveraging binder vulnerabilities and process injection. The code is operational and provides a working shell as system_server if successful, but requires adaptation for other devices or Android versions.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.