CVE-2018-16081
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…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.06%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.0
- 7.4 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
- EPSS
- 1.06% probability · 63th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-862
- Affected
- google/chrome · redhat/enterprise linux desktop · redhat/enterprise linux server · redhat/enterprise linux workstation
- Source
- chrome-cve-admin@google.com
References
- http://www.securityfocus.com/bid/105215
- https://access.redhat.com/errata/RHSA-2018:2666
- https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html
- https://crbug.com/666299
- https://security.gentoo.org/glsa/201811-10
- http://www.securityfocus.com/bid/105215
- https://access.redhat.com/errata/RHSA-2018:2666
- https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html
- https://crbug.com/666299
- https://security.gentoo.org/glsa/201811-10
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.