Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Integer overflow in V8 object allocation in Google Chrome

IdentifiersCVE-2018-6065CWE-190· Integer Overflow or Wraparound

CVE-2018-6065 is an integer overflow vulnerability in the V8 JavaScript engine in Google Chrome prior to 65.0.3325.146. The flaw occurs while computing the required allocation size when instantiating a new JavaScript object. A crafted HTML page can trigger the overflow, leading to an undersized or otherwise incorrect heap allocation and subsequent heap corruption during object creation.

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 can cause heap corruption in the Chrome renderer process. In practice, this may allow a remote attacker to achieve code execution in the context of the targeted browser process via malicious web content. At minimum, the flaw provides a path to memory corruption and potential browser compromise when a victim visits an attacker-controlled page.

Mitigation

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

If immediate patching is not possible, reduce exposure by restricting access to untrusted websites, disabling or tightly controlling use of vulnerable Chrome versions, and using application isolation/sandboxing controls where available. Enterprise controls such as URL filtering, browser version enforcement, and exploit-detection telemetry may reduce risk, but they are not substitutes for patching.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 65.0.3325.146 or later, which contains the vendor patch for CVE-2018-6065. Ensure Chromium-based deployments and embedded Chrome/WebView components are updated to builds incorporating the fix. Standard patch-management controls should prioritize browsers exposed to untrusted web content.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

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
XiaomiMi6 Browserapplication

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.