Use-After-Free in FileAPI in Google Chrome < 72.0.3626.81
A use-after-free vulnerability exists in the FileAPI implementation in Google Chrome prior to version 72.0.3626.81. The flaw allows a remote attacker to trigger a use-after-free condition by enticing a user to visit a specially crafted HTML page, potentially leading to memory corruption and arbitrary code execution within the context of the browser sandbox.
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 allows a remote attacker to execute arbitrary code in the context of the browser process, potentially leading to a sandbox escape. This could allow further compromise of the system depending on the attacker's ability to chain with other vulnerabilities.
If you can’t patch tonight, do this now.
As a temporary mitigation, restrict access to untrusted web content and disable JavaScript where feasible. Employ browser sandboxing and application whitelisting to limit the impact of potential exploitation.
Patch, then assume compromise.
Upgrade to Google Chrome version 72.0.3626.81 or later, where the vulnerability has been patched.
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.