Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

V8 out-of-bounds write via JavaScript during array deserialization in Google Chrome

IdentifiersCVE-2018-17480CWE-787· Out-of-bounds Write

CVE-2018-17480 is an out-of-bounds write vulnerability in the V8 JavaScript engine in Google Chrome prior to 71.0.3578.80. According to the provided content, the flaw is triggered by execution of user-supplied JavaScript during array deserialization, resulting in memory corruption in V8. A remote attacker can deliver the trigger through a crafted HTML page and achieve arbitrary code execution within the Chrome renderer sandbox.

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 code execution in the context of the Chrome sandboxed renderer process. This enables an attacker to run arbitrary code after a victim visits a malicious web page. Because the provided content specifies execution inside a sandbox, full system compromise would generally require an additional sandbox escape or privilege-escalation step not described here.

Mitigation

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

Until patching is completed, reduce exposure by restricting access to untrusted websites, disabling or tightly controlling use of vulnerable Chrome versions on exposed endpoints, and using browser isolation or application sandbox hardening where available. Enterprise controls that limit renderer-to-system post-exploitation paths can reduce impact, but they do not remove the underlying vulnerability.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 71.0.3578.80 or later, as the vulnerability affects versions prior to 71.0.3578.80. Ensure Chromium-based deployments and embedded Chrome components are updated to builds containing the V8 fix.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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.