Loading vulnerability…
CVE-2023-45779 is a local privilege escalation vulnerability in the APEX module framework of the Android Open Source Project. The issue is caused by improperly used cryptography in the update mechanism for platform components, creating a condition in which a malicious update to platform components may be accepted or applied. Successful exploitation does not require user interaction and can allow an attacker operating locally on the device to elevate privileges.
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 provides a proof-of-concept (PoC) exploit and detection toolkit for a class of Android vulnerabilities where APEX modules are signed with publicly known AOSP test keys. The exploit demonstrates that, on affected devices, an attacker with ADB access can extract a vulnerable APEX (such as com.android.vndk.*), modify it to include a malicious shared library (libt.so), patch the APEX to load this library, and re-sign it with the test keys. The forged APEX is then installed and, upon reboot, the injected library is loaded by various system processes, logging their command lines to logcat as proof of code execution. The repository includes Bash scripts for key management and APEX manipulation, a C payload for the injected library, and documentation. The attack vector is local, requiring physical or ADB access to the device. The main fingerprintable endpoints are the APEX files on the device and the /proc/self/cmdline file accessed by the payload. The exploit is a PoC and does not provide a weaponized or easily customizable payload, but it clearly demonstrates the risk of shipping APEX modules signed with test keys.
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.