First published: Wed Sep 05 2018(Updated: )
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.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/chromium-browser | <69.0.3497.81 | 69.0.3497.81 |
Google Chrome | <69.0.3497.81 | |
redhat enterprise Linux desktop | =6.0 | |
redhat enterprise Linux server | =6.0 | |
redhat enterprise Linux workstation | =6.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-16081 is considered a high severity vulnerability due to its potential to allow unauthorized file system access.
To fix CVE-2018-16081, update your Google Chrome or Chromium Browser to version 69.0.3497.81 or later.
CVE-2018-16081 affects users of Google Chrome versions prior to 69.0.3497.81 and Chromium Browser versions below that threshold.
CVE-2018-16081 enables an attacker to access local files by convincing a user to install a malicious Chrome extension.
Yes, the risk with CVE-2018-16081 includes potential data breaches and unauthorized access to sensitive files on a user's local system.