Loading vulnerability…
CVE-2023-42470 is a remote code execution vulnerability in the Imou Life (com.mm.android.smartlifeiot) Android application up to version 6.8.0. The vulnerability exists in the exported com.mm.android.easy4ip.MainActivity activity, which allows external applications to send crafted intents. The activity contains a WebView with JavaScript execution enabled and loads web content directly, allowing an attacker to execute arbitrary JavaScript and potentially achieve code execution in the app's context.
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 documents two Android application vulnerabilities affecting Dahua Imou Life apps. Each file is a markdown report with technical details and proof-of-concept (PoC) code: 1. **com.dahua.imou.go-V1.0.11.md** describes a vulnerability in the `com.dahua.imou.go` app's `DownloadFirmwareService`. The service accepts firmware download URLs from intents without validation, allowing a malicious app to trigger the download and execution of arbitrary firmware. The PoC demonstrates both Java code and an adb command to exploit this flaw. The main attack vector is local (malicious app on the same device), and the endpoint is the exported Android service. 2. **imou-life-6.8.0.md** details a vulnerability in the `com.mm.android.smartlifeiot` app's `MainActivity`, which is exported and loads URLs from intent data directly into a WebView with JavaScript enabled. This allows a malicious app to trigger the loading of attacker-controlled web content, potentially leading to JavaScript-based attacks or remote code execution. The PoC shows how to craft an intent to exploit this behavior. The main attack vector is also local, and the endpoint is the exported activity. Both vulnerabilities allow for arbitrary code execution or device compromise via malicious apps, without requiring special permissions. The repository provides clear technical explanations, PoC code, and remediation recommendations. No actual exploit code is present beyond the PoC intent triggers, and no detection scripts are included.
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.