Out-of-bounds write in Google Chrome JavaScript
CVE-2019-5825 is an out-of-bounds write vulnerability in the JavaScript engine of Google Chrome prior to version 73.0.3683.86. The provided content states that a remote attacker could trigger heap corruption via a crafted HTML page. The vulnerability was used as one of several Android Chrome browser exploits in the MOONSHINE framework, and the referenced exploit was reportedly based on exploit code published by Exodus Intelligence after identifying a Chrome JavaScript-engine flaw that had been fixed in source code before the patch had shipped broadly to users.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a working exploit for CVE-2019-5825, a vulnerability in Google Chrome's V8 JavaScript engine (version 6.9.0, as shipped with Chrome 73.0.3683.86). The exploit targets the browser in --no-sandbox mode and achieves arbitrary read/write (AARW) in the V8 heap by corrupting array lengths and object pointers via a crafted Array.map call. The main exploit logic is implemented in 'exodus.js', which demonstrates the full chain from bug trigger to shellcode execution by abusing a WebAssembly instance to obtain a RWX memory page. The shellcode is injected and executed, resulting in remote code execution. Supporting files include 'exploit.js' and 'nextline.js', which are alternative or simplified exploit scripts for the same vulnerability, and 'exploit.sh', a Bash script to automate testing on both ia32 and x64 V8 d8 shells. The repository is operational and provides a full exploit chain, including payload delivery. No network endpoints or external services are targeted; the exploit is local to the browser or JavaScript engine process. The code is well-structured, with clear separation between helper functions, exploit primitives, and payload delivery.
Affected products & vendors
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.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Google Chrome vulnerability used by POISON CARP in MOONSHINE; exploit code was publicly released before the patch had reached Chrome users.
A Google Chrome vulnerability for which Exodus Intelligence published working exploit code; used by MOONSHINE against vulnerable Android Chrome versions.
The version that knows your environment.
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.