Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Type confusion in V8 in Google Chrome

IdentifiersCVE-2018-17463CWE-913

CVE-2018-17463 is a V8 engine vulnerability in Google Chrome caused by an incorrect side-effect annotation in the optimizing compiler pipeline. According to the provided content, affected Chrome versions prior to 70.0.3538.64 could be induced via a crafted HTML page to reach a state that allowed arbitrary code execution inside the Chrome sandbox. The issue was used as one of several Android Chrome browser exploits in the MOONSHINE exploitation framework, where exploit selection was mapped to the victim’s Chrome version. The provided material does not identify the exact vulnerable function beyond the V8 side-effect annotation flaw.

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 remote arbitrary code execution in the context of the Chrome renderer sandbox when a target visits attacker-controlled web content. In the campaign context provided, this capability was used as an initial browser compromise step on Android devices to stage additional malware delivery. Because execution is described as occurring inside the sandbox, additional escape or privilege-escalation steps would generally be required for full device compromise, but sandboxed code execution is sufficient to run attacker-supplied logic in the browser process and facilitate follow-on exploitation or payload staging.

Mitigation

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

Until patching is complete, reduce exposure by restricting access to untrusted or attacker-controlled web content, especially links delivered through messaging platforms or social engineering. On mobile devices, limit or disable use of in-app browsers/webviews where operationally feasible, since the campaign described attempted to force malicious URLs into Facebook’s built-in Chrome-based browser. Enterprise controls such as URL filtering, mobile threat defense, application allowlisting, and rapid browser update enforcement can reduce exploitation opportunities, but these are compensating controls and not substitutes for upgrading to a fixed Chrome version.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 70.0.3538.64 or later, as the vulnerability affected versions prior to 70.0.3538.64. On managed Android fleets, ensure Chrome/WebView updates are promptly deployed through the relevant app distribution channel and verify that devices are no longer running vulnerable builds. Where applicable, update any embedded Chromium-based browsers that inherit the vulnerable V8 version.
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 evidence2

Every observed campaign linking this CVE to a named adversary.

Associated malware3

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.