Type confusion in V8 in Google Chrome
CVE-2016-5198 is a V8 engine vulnerability in Google Chrome caused by incorrect optimisation assumptions. In affected Chrome versions prior to 54.0.2840.90 on Linux, 54.0.2840.85 on Android, and 54.0.2840.87 on Windows and macOS, a remote attacker could trigger unsafe V8 behavior via crafted HTML/JavaScript, resulting in arbitrary read and write primitives in the renderer process. Those memory corruption primitives could then be used to achieve code execution. The issue was exploitable through a malicious web page and was used as part of Android exploitation frameworks such as MOONSHINE to target vulnerable Chromium-based browsers.
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
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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
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 #2 in the MOONSHINE Android exploit kit.
A Chromium vulnerability targeted by the MOONSHINE exploit kit against Android apps embedding vulnerable Chrome 50.
A Google Chrome vulnerability leveraged by MOONSHINE to compromise Android devices running affected 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.