Loading vulnerability…
A vulnerability in AppRestrictionsFragment.java in Android (versions 10, 11, 12, 12L) allows a local attacker to start a phone call without the necessary permissions by exploiting a confused deputy issue. The vulnerable function, assertSafeToStartCustomActivity, fails to properly validate the caller's permissions, enabling privilege escalation without user interaction.
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 contains a proof-of-concept exploit for a custom vulnerable Flask server intended to run on an Android device (likely within Termux). The repository consists of three files: 'exploit.sh' (the main exploit script), 'server.py' (the vulnerable server), and 'requirements.txt' (Python dependencies for the server). The exploit works by prompting the attacker for the target's IP and port, then starting a netcat listener on the attacker's machine. It encodes a bash reverse shell payload in base64 and sends it via a POST request to the '/api/vulnerable_endpoint' endpoint on the target. The vulnerable server decodes the payload, writes it to a shell script in the Termux home directory, and executes it, resulting in a reverse shell connection back to the attacker. The main attack vector is network-based, targeting a specific HTTP API endpoint. The exploit is operational, providing a working reverse shell if the vulnerable server is running and accessible.
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.