CVE-2018-16081
N/A
Published: January 9, 2019 at 07:00 PM UTC
Updated: June 17, 2026 at 01:43 AM UTC
4 products affected across 2 vendorsChromeEnterprise Linux DesktopEnterprise Linux Server
Using Chrome by Google?
Get instant alerts when new vulnerabilities affect Chrome - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 1%
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.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
v < 69.0.3497.81
Affected range stops below 69.0.3497.81, so it looks safe — our inference, not a vendor statement
95%
Enterprise Linux Server· Red Hatrubygems
95%95%
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (5)
Vendor Advisoryx_refsource_REDHAT
Source: [email protected]
https://access.redhat.com/errata/RHSA-2018:2666x_refsource_CONFIRMx_refsource_MISC
Source: [email protected]
https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.htmlVendor Advisoryx_refsource_GENTOO
Source: [email protected]
https://security.gentoo.org/glsa/201811-10Quick Info
StatusMODIFIED
CWE
CWE-862
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card