CVE-2017-5030 is a remote code execution vulnerability in the V8 JavaScript engine in Google Chrome caused by incorrect handling of complex species. According to the provided content, affected versions are Chrome prior to 57.0.2987.98 on Linux, Windows, and macOS, and prior to 57.0.2987.108 on Android. A remote attacker can trigger the flaw by convincing a victim to load a crafted HTML page, leading to arbitrary code execution in the browser context. The content specifically identifies the bug as residing in V8’s handling of complex species, but does not provide the exact vulnerable function or code path.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Google Chrome vulnerability used as Exploit #3 in the MOONSHINE Android exploit kit.
A Chromium vulnerability targeted by the MOONSHINE exploit kit against Android apps embedding vulnerable Chrome versions 51 through 55.
A Google Chrome vulnerability used within MOONSHINE to exploit specific Android Chrome versions.
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.