Loading vulnerability…
CVE-2019-11931 is a stack-based buffer overflow vulnerability in WhatsApp, triggered by parsing the elementary stream metadata of a specially crafted MP4 file. The flaw exists in the code responsible for handling MP4 files, where improper bounds checking allows an attacker to overwrite stack memory. This vulnerability affects WhatsApp for Android versions prior to 2.19.274, iOS versions prior to 2.19.100, Enterprise Client versions prior to 2.25.3, Business for Android versions prior to 2.19.104, and Business for iOS versions prior to 2.19.100.
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 single C source file ('standalone.c') and a .gitignore. The exploit is a proof-of-concept targeting the WhatsApp Android application by dynamically loading the WhatsApp native library (libwhatsapp.so) from a user-specified path (via the WHATSAPPLIB environment variable). It locates the 'Java_com_whatsapp_Mp4Ops_mp4check' function and calls a function at a fixed offset from this symbol, passing a user-supplied filename and a timespec structure. This is likely intended to trigger or test a vulnerability in WhatsApp's media file processing. The exploit must be run on a system where the WhatsApp library is present and accessible. No network endpoints are involved; the attack vector is local, requiring access to the device and the WhatsApp library. The repository is structured as a minimal proof-of-concept for vulnerability research or testing.
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.