CVE-2018-16081 Security feature bypass in Chrome

High 7.4 Published Updated

A malicious Chrome extension can bypass file access permissions to read local files via the debugger API, requiring user installation of the extension.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2018-16081?

CVE-2018-16081 is a high-severity vulnerability in Google Chrome, published on 9 Jan 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official 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.

Weakness: CWE-862

Which versions are affected by CVE-2018-16081?

It affects 4 products.

Products include Google Chrome, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.

How do I fix CVE-2018-16081?

Upgrade to a fixed version.

Is CVE-2018-16081 being exploited?

There is no known exploitation of CVE-2018-16081 in the wild and no public exploit code.

All Google Chrome vulnerabilities

Sources

Also known as GHSA-h5rc-j9f7-wmr8, UBUNTU-CVE-2018-16081.

Is CVE-2018-16081 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free