Heap Buffer Overflow in Vulkan in Google Chrome <107.0.5304.62
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.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation of this vulnerability could allow a remote attacker to achieve heap corruption, which may lead to arbitrary code execution in the context of the browser. This could result in full compromise of the affected user's system if chained with other vulnerabilities or sandbox escapes.
If you can’t patch tonight, do this now.
As a temporary mitigation, users can disable WebGL or restrict access to untrusted web content. Employing browser sandboxing and keeping the browser up to date will reduce the risk of exploitation.
Patch, then assume compromise.
Upgrade Google Chrome to version 107.0.5304.62 or later, where this vulnerability has been addressed by proper bounds checking and memory management in the Vulkan component.
1 exploit validated by Mallory's analysis.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.