Loading vulnerability…
CVE-2019-5786 is an object lifetime vulnerability in Blink, the Chromium and Google Chrome rendering engine, affecting Google Chrome prior to 72.0.3626.121. The flaw is associated with the FileReader API and can be triggered while rendering attacker-controlled HTML content. Improper object lifetime handling can lead to out-of-bounds memory access during page processing. Available reporting indicates the issue was exploited in the wild as a Chrome zero-day, and that successful exploitation could be chained to achieve code execution beyond the browser sandbox on the host system.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module: 'chrome_filereader_uaf.rb', which exploits a use-after-free vulnerability (CVE-2019-5786) in Google Chrome 72.0.3626.119 on Windows 7 x86. The exploit leverages a flaw in the FileReader.readAsArrayBuffer function, allowing arbitrary memory access via JavaScript. The module sets up an HTTP server that serves a crafted HTML/JavaScript payload ('/exploit.html') and a supporting worker script ('/worker.js') to the target browser. Successful exploitation results in arbitrary code execution within the Chrome process, typically delivering a Meterpreter reverse shell. The exploit requires the Chrome sandbox to be disabled for the payload to execute. The code is operational and customizable within the Metasploit framework, targeting a specific Chrome version on Windows 7 x86.
This repository contains a proof-of-concept exploit for CVE-2019-5786, a use-after-free vulnerability in the FileReader component of Google Chrome 72.0.3626.119 on Windows 7 x86. The exploit is implemented in JavaScript and HTML files. The main files are: - exploit.html: Loads exploit.js and triggers the exploit on page load. - exploit.js: Contains the core logic for heap spraying, triggering the use-after-free, and achieving arbitrary memory read/write in the browser process. - iframe.html: Acts as a wrapper to repeatedly load the exploit in an iframe, facilitating brute-force exploitation across site isolation boundaries. The URL of exploit.html must be set in this file. - worker.js: A minimal web worker script used as part of the exploitation process. The README provides setup instructions, requiring the exploit to be hosted across two origins and Chrome to be started with the --no-sandbox flag. The exploit is a POC and does not include a weaponized payload, but demonstrates the ability to achieve arbitrary memory access, which can be leveraged for further exploitation such as remote code execution. The only hardcoded endpoint is 'http://127.0.0.1/exploit.html', which is used as the default target for the iframe loader.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.