Loading vulnerability…
CVE-2018-9411 is an out-of-bounds write vulnerability in Android's Media Framework, specifically in the decrypt function of ClearKeyCasPlugin.cpp. The flaw is caused by a missing bounds check during decryption processing, allowing memory to be written past the intended buffer boundary. According to the provided description, successful exploitation could result in remote arbitrary code execution. Exploitation requires 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 (PoC) exploit for CVE-2018-9411, a critical vulnerability in the Android MediaCasService. The exploit is specifically tailored for the Google Pixel 2 device running the May 2018 security update (build OPM2.171019.029.B1/4720900). The main exploit logic resides in 'cas_exploit.cpp', which leverages a heap out-of-bounds copy vulnerability to manipulate thread states and execute a ROP chain. The exploit interacts with the MediaCasService and the TEE device via the /dev/qseecom device file, ultimately leaking the QSEOS version as proof of successful exploitation. The repository includes supporting header files for device-specific offsets and QSEE communication structures. The exploit requires building within the Android Open Source Project (AOSP) environment and is not a generic exploit, but a targeted PoC for a specific device and firmware version. No network endpoints are involved; the attack vector is local, requiring code execution on the target device.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.