Heap Corruption in V8 (Google Chrome < 80.0.3987.162)
CVE-2020-6453 is a vulnerability in the V8 JavaScript engine in Google Chrome prior to version 80.0.3987.162. The issue arises from an inappropriate implementation that allows a remote attacker to trigger heap corruption by enticing a user to visit a specially crafted HTML page. The vulnerability is likely due to improper memory handling in V8, which could lead to memory corruption when processing malicious JavaScript.
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 execute arbitrary code in the context of the browser, potentially leading to full compromise of the affected system if chained with a sandbox escape. The attacker would only need to convince a user to visit a malicious web page.
If you can’t patch tonight, do this now.
As a temporary mitigation, users can disable JavaScript or use browser security extensions to limit the execution of untrusted scripts. Restricting access to untrusted websites and employing endpoint security solutions may also reduce the risk of exploitation until the browser is updated.
Patch, then assume compromise.
Upgrade Google Chrome to version 80.0.3987.162 or later, which contains the fix for this vulnerability. Users and administrators should ensure automatic updates are enabled to receive security patches promptly.
No public exploits tracked yet. Mallory keeps watching.
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.