Loading vulnerability…
A heap buffer overflow vulnerability exists in the Vulkan component of Google Chrome prior to version 107.0.5304.62. The vulnerability can be triggered by a remote attacker through a crafted HTML page, leading to potential heap corruption. This issue is due to improper handling of memory boundaries in the Vulkan implementation within Chromium.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single C++ proof-of-concept (PoC) exploit for CVE-2022-3653, a heap buffer overflow vulnerability in Google's ANGLE (Almost Native Graphics Layer Engine) Vulkan backend when using multiview rendering. The exploit demonstrates how to trigger the vulnerability by creating a Vulkan instance, enabling multiview, allocating a query pool, and then performing a sequence of Vulkan API calls that result in an out-of-bounds write in SwiftShader's QueryPool::begin() function. The code is well-commented and provides detailed output about each step, including checks for multiview support and explanations of where the overflow occurs. The exploit is a local PoC and does not interact with network endpoints; it targets systems with a vulnerable ANGLE Vulkan backend and is intended for research and testing purposes.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.