Loading vulnerability…
CVE-2024-0015 is a vulnerability in the convertToComponentName function of DreamService.java in Android. The vulnerability arises from improper handling of Intents, allowing an attacker to redirect Intents to arbitrary protected activities. This can be exploited locally to launch activities that should be protected, bypassing intended security boundaries.
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-2024-0015, as indicated in the README. The project is structured as a standard Android Studio project, with the main code in 'app/src/main/java/com/tsctf/daydream/'. The two main Java files are 'MainActivity.java' (the app's main activity) and 'MyService.java', which implements a DreamService. The AndroidManifest.xml registers 'MyService' as an exported DreamService with the BIND_DREAM_SERVICE permission, and references a metadata file ('test_dream_metadata.xml') that points to a settings activity in another app ('com.tsctf.victimapp/.SecretActivity'). This setup suggests the exploit leverages the DreamService framework to interact with or trigger behavior in another app, likely exploiting improper component exposure or privilege escalation. The repository contains all standard Android project files, resources, and build scripts, but the exploit logic is centered around the DreamService registration and its interaction with the victim app's component. No network endpoints are present; the attack vector is local, targeting Android's inter-process communication and component exposure.
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.