CVE-2018-16081: High severity Google Chrome vulnerability
A local file access flaw was found in the DevTools component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=666299
External References:
https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/chromium-browserto a version that resolves this vulnerability.Fixed in 69.0.3497.81 - Upgrade
Upgrade
Google Chrometo a version that resolves this vulnerability.Fixed in 69.0.3497.81
Event History
Frequently Asked Questions
What is the severity of CVE-2018-16081?
CVE-2018-16081 is considered a high severity vulnerability due to its potential to allow unauthorized file system access.
How do I fix CVE-2018-16081?
To fix CVE-2018-16081, update your Google Chrome or Chromium Browser to version 69.0.3497.81 or later.
Who is affected by CVE-2018-16081?
CVE-2018-16081 affects users of Google Chrome versions prior to 69.0.3497.81 and Chromium Browser versions below that threshold.
What type of attack does CVE-2018-16081 enable?
CVE-2018-16081 enables an attacker to access local files by convincing a user to install a malicious Chrome extension.
Is there any potential risk with CVE-2018-16081?
Yes, the risk with CVE-2018-16081 includes potential data breaches and unauthorized access to sensitive files on a user's local system.