Loading vulnerability…
CVE-2024-0039 is an out-of-bounds write vulnerability in the Android System component's attp_build_value_cmd function in att_protocol.cc. The flaw results from a missing bounds check and can be exploited remotely to achieve code execution without additional execution privileges or 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 is a Python-based exploit for CVE-2024-0039, a vulnerability affecting certain Android devices. The main script, 'exploit.py', generates a malicious MP4 file containing a buffer overflow payload, a ROP chain, and a reverse shell. The attacker specifies a callback host and port, which are embedded into the payload to establish a reverse shell connection upon successful exploitation. The exploit is operational: it creates a real payload, but the ROP chain and shellcode are placeholders and may require adaptation for a real-world attack. The repository is well-structured, with helper functions in 'utils/helpers.py' and unit tests in 'tests/expoit.test.py'. The exploit logs its actions to 'logs/exploit.log'. No hardcoded IPs or domains are present; the attacker supplies these at runtime. The exploit targets Android devices vulnerable to CVE-2024-0039 and is intended for educational purposes.
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.