Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighCISA KEVExploited in the wildPublic exploit

Type Confusion RCE in Google Chrome V8

IdentifiersCVE-2018-17463CWE-843

CVE-2018-17463 is a V8 engine vulnerability in Google Chrome caused by an incorrect side-effect annotation in the optimizing compiler/JIT pipeline. In Chrome versions prior to 70.0.3538.64, this flaw can lead to type confusion during JavaScript optimization when processing attacker-controlled script delivered through a crafted HTML page. The issue is in V8 rather than a renderer-independent component, and successful triggering allows arbitrary code execution within the Chrome sandbox. Reporting in the provided context also shows the bug was incorporated into the MOONSHINE exploit framework to target vulnerable Chrome 68 and 69 builds on Android/Chromium-based environments.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation allows a remote attacker to execute arbitrary code in the context of the Chrome renderer sandbox. This can be used to compromise the browser process handling malicious content and, in real-world exploit chains, to stage additional payload delivery, spyware installation, or further sandbox-escape/privilege-escalation steps. By itself, the documented impact is code execution inside the sandbox rather than full system compromise.

Mitigation

If you can’t patch tonight, do this now.

Until patching is complete, reduce exposure by restricting use of vulnerable Chrome/Chromium versions, especially Chrome 68–69 as referenced in the observed exploitation context. Limit access to untrusted links and attacker-controlled web content, disable or constrain use of outdated embedded browsers/webviews where feasible, and use application control, mobile device management, and exploit-detection/EDR controls to detect abnormal browser child-process behavior or post-exploitation payload delivery. Because exploitation is via crafted HTML, network filtering and user-awareness measures can reduce opportunistic exposure but are not substitutes for patching.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 70.0.3538.64 or later, which contains the fix for CVE-2018-17463. On Android and embedded Chromium-based applications, ensure the underlying browser engine/WebView or bundled Chromium component is updated to a non-vulnerable version. Where third-party apps embed outdated Chromium components, update the application itself or replace it if the vendor no longer provides security updates.
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 2 / 2 TOTALView more in app
CVE-2018-17463MaturityPoCVerified exploit

This repository contains a working exploit for CVE-2018-17463, a vulnerability in the V8 JavaScript engine (used in Google Chrome). The main file, CVE-2018-17463.js, is a standalone JavaScript exploit that demonstrates how to achieve arbitrary read/write primitives and ultimately execute arbitrary code by spawning a /bin/sh shell. The exploit works by manipulating object properties to create overlapping memory regions, leveraging JIT (Just-In-Time) compilation behaviors, and constructing a ROP (Return-Oriented Programming) chain to make memory pages executable and run shellcode. The shellcode is provided as a byte array and is executed to spawn a shell, demonstrating full code execution. The README provides references to relevant research and writeups. The exploit is operational and demonstrates a full exploit chain, but is not part of a framework and is intended for research and demonstration purposes. The only fingerprintable endpoint is the use of /bin/sh in the shellcode payload.

kdmarti2Disclosed May 2, 2021javascriptmarkdownlocal
CVE-2018-17463MaturityPoCVerified exploit

This repository contains a working proof-of-concept exploit for CVE-2018-17463, a vulnerability in the V8 JavaScript engine used by Google Chrome prior to version 70.0.3538.64. The exploit is implemented in a single JavaScript file (CVE-2018-17463.js) and leverages a type confusion bug to achieve arbitrary memory read and write primitives. It then uses WebAssembly to allocate a RWX (read-write-execute) memory region, writes x86_64 shellcode to this region, and executes it, resulting in arbitrary code execution (demonstrated by launching calc.exe). The exploit demonstrates advanced exploitation techniques including property overlap discovery, address leaking, and memory corruption. The README provides context, references, and credits, but the main exploit logic is self-contained in the JavaScript file. No network or external endpoints are hardcoded in the exploit; it is designed to be run in a browser context where the vulnerable V8 engine is present.

jhalonDisclosed Dec 28, 2022javascriptbrowser
EXPOSURE SURFACE

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.

VendorProductType
DebianDebian Linuxoperating_system
GoogleChromeapplication
Red HatEnterprise Linux Desktopoperating_system
Red HatEnterprise Linux Serveroperating_system
Red HatEnterprise Linux Workstationoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence3

Every observed campaign linking this CVE to a named adversary.

Associated malware5

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.