published 9 Jan 2019 · updated 5 Aug 2024
Allowing the chrome.debugger API to run on file:// URLs in DevTools in Google Chrome prior to 69.0.3497.81 allowed an attacker who…
5.0MediumEPSS 1%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Chrome 69.0.3497.81.
Allowing the chrome.debugger API to run on file:// URLs in DevTools in Google Chrome prior to 69.0.3497.81 allowed an attacker who convinced a user to install a malicious extension to access files on the local file system without file access permission via a crafted Chrome Extension.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Chrome | <69.0.3497.81 | 69.0.3497.81 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Chrome, strongest first
Embed
A live severity badge for an advisory, README or ticket