Heap Buffer Overflow in Skia in Google Chrome
CVE-2024-8636 is a heap buffer overflow vulnerability in Skia, the graphics library used by Google Chrome. According to the provided content, affected versions are Google Chrome prior to 128.0.6613.137. The issue can be triggered by a remote attacker via a crafted HTML page, leading to heap corruption. No specific vulnerable function or code path is provided in the supplied content.
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.
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.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (PoC) exploit for a vulnerability in the GPU process of Chromium/Chrome browsers prior to version 128. The exploit consists of four files: - README.txt: Provides step-by-step instructions to reproduce the issue, including applying a patch, generating a payload, and triggering the bug. - chromium.diff: A patch to Chromium's raster_implementation.cc, which adds code to load a crafted Skia picture and send it to the GPU process in a specific way, potentially triggering a vulnerability. - genskpic.py: A Python script that generates a malicious Skia picture file (pic.skp) and a corresponding C++ header (drawable_picture.skp.hh) containing the payload as a byte array. - index.html: A minimal HTML/JavaScript file that, when loaded in the patched browser, triggers the vulnerable code path by drawing many rectangles on a canvas. The exploit demonstrates a GPU process crash (denial of service) by abusing the way Skia picture data is handled in the browser's GPU rasterization code. The exploit is not weaponized for code execution but serves as a PoC for the underlying vulnerability. No network endpoints or external services are involved; the attack vector is via local browser rendering. The exploit targets Google Chrome and Chromium browsers prior to version 128, as the issue is noted as fixed in M128.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.