Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Out-of-bounds write in Dawn in Google Chrome

IdentifiersCVE-2024-10487CWE-787· Out-of-bounds Write

CVE-2024-10487 is a critical memory-safety vulnerability in the Dawn component of Google Chrome. According to the provided content, Chrome versions prior to 130.0.6723.92 contain an out-of-bounds write condition that can be triggered by a crafted HTML page, resulting in out-of-bounds memory access. Dawn is Chromium’s WebGPU implementation layer, so exploitation would occur in browser processing of attacker-controlled web content. No specific vulnerable function or code path was provided in the supplied material.

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 could allow a remote attacker to corrupt memory in the browser process through malicious web content. Given the out-of-bounds write condition and Chrome’s critical severity rating, the likely impact includes browser crash, denial of service, and potential arbitrary code execution depending on exploit reliability and surrounding mitigations. The provided content does not specify whether exploitation escapes the browser sandbox.

Mitigation

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

Primary mitigation is prompt patching to Chrome 130.0.6723.92 or later. Until updates are fully deployed, reduce exposure to untrusted web content, restrict browsing to trusted sites where feasible, and consider limiting or disabling access to browser features that exercise the affected rendering/GPU pathways if operationally possible. No specific vendor workaround was provided in the supplied content.

Remediation

Patch, then assume compromise.

Update Google Chrome to version 130.0.6723.92 or later, as the issue affects versions prior to 130.0.6723.92. Apply the vendor-provided stable-channel update across affected systems and ensure Chromium-based downstream products are updated once vendor fixes are available if they incorporate the vulnerable code.
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
GoogleChromeapplication

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

ACTIVITY FEED

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

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 evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

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.