A use-after-free vulnerability exists in the ClearKey CAS descrambler component of Android versions 8.0, 8.1, and 9. The flaw is caused by a race condition, which can result in the use of memory after it has been freed. This vulnerability can be exploited locally to escalate privileges without requiring user interaction or additional execution 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 contains a proof-of-concept (PoC) exploit for CVE-2018-9539, a use-after-free (UAF) vulnerability in the Android Media CAS (Conditional Access System) service. The exploit is implemented in a single C++ file (cas_race_uaf.cpp) and is designed to be built as part of the Android Open Source Project (AOSP) external modules. The exploit works by creating two CAS sessions, assigning one to a descrambler, and then racing multiple threads that call the descramble method while switching the descrambler's session to the second session. This race condition can trigger a UAF, causing the service to crash, as demonstrated in the provided output. The exploit targets Android versions 8.1 and 9.0 prior to the November 2018 security patch. The repository includes build instructions and a README with example output. No network endpoints are involved; the attack vector is local, requiring code execution privileges 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.
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.