CVE-2018-6109: Infoleak
First published: Mon Apr 10 2017(Updated: )
readAsText() can indefinitely read the file picked by the user, rather than only once at the time the file is picked in File API in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to access data on the user file system without explicit consent via a crafted HTML page.
Credit: Dominik Weber @DoWeb_ cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/chromium-browser | ||
| redhat/chromium-browser | <66.0.3359.117 | 66.0.3359.117 |
| Google Chrome | <66.0.3359.117 | 66.0.3359.117 |
| Google Chrome | <66.0.3359.117 | |
| Debian Debian Linux | =8.0 | |
| Debian Debian Linux | =9.0 | |
| redhat enterprise Linux desktop | =6.0 | |
| redhat enterprise Linux server | =6.0 | |
| redhat enterprise Linux workstation | =6.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html (Advisory)
- http://www.securityfocus.com/bid/103917
- https://access.redhat.com/errata/RHSA-2018:1195
- https://crbug.com/710190
- https://security.gentoo.org/glsa/201804-22
- https://www.debian.org/security/2018/dsa-4182
- https://code.google.com/p/chromium/issues/detail?id=710190
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1568801
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1568800
- https://bugzilla.redhat.com/show_bug.cgi?id=1568789
- https://security-tracker.debian.org/tracker/CVE-2018-6109
Peer vulnerabilities
(Found alongside the following vulnerabilities)
- CVE-2018-6085
- CVE-2018-6086
- CVE-2018-6087
- CVE-2018-6088
- CVE-2018-6089
- CVE-2018-6090
- CVE-2018-6091
- CVE-2018-6092
- CVE-2018-6093
- CVE-2018-6152
- CVE-2018-6094
- CVE-2018-6095
- CVE-2018-6150
- CVE-2018-6096
- CVE-2018-6097
- CVE-2018-6151
- CVE-2018-6098
- CVE-2018-6099
- CVE-2018-6100
- CVE-2018-6101
- CVE-2018-6102
- CVE-2018-6103
- CVE-2018-6104
- CVE-2018-6105
- CVE-2018-6106
- CVE-2018-6107
- CVE-2018-6108
- CVE-2018-6110
- CVE-2018-6111
- CVE-2018-6112
- CVE-2018-6113
- CVE-2018-6114
- CVE-2018-6115
- CVE-2018-6116
- CVE-2018-6117
- CVE-2018-6084
Frequently Asked Questions
What is the severity of CVE-2018-6109?
CVE-2018-6109 is classified as a high-severity vulnerability due to its potential to allow unauthorized access to the user's file system.
How do I fix CVE-2018-6109?
To mitigate CVE-2018-6109, upgrade Google Chrome or Chromium to version 66.0.3359.117 or later.
Which versions of Google Chrome are affected by CVE-2018-6109?
Google Chrome versions prior to 66.0.3359.117 are affected by CVE-2018-6109.
Is CVE-2018-6109 specific to any operating system?
CVE-2018-6109 affects Google Chrome across multiple operating systems, including Windows, macOS, and Linux.
What types of attacks can exploit CVE-2018-6109?
CVE-2018-6109 can be exploited via crafted HTML pages to gain unauthorized access to user files.
- collector/security-tracker-debian
- agent/type
- agent/first-publish-date
- agent/weakness
- agent/severity
- agent/references
- agent/author
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2018-6109
- agent/software-canonical-lookup
- collector/chrome-releases
- agent/software-canonical-lookup-request
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/description
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/softwarecombine
- package-manager/debian
- package-manager/redhat
- vendor/google
- canonical/google chrome
- vendor/debian
- canonical/debian debian linux
- version/debian debian linux/8.0
- version/debian debian linux/9.0
- vendor/redhat
- canonical/redhat enterprise linux desktop
- version/redhat enterprise linux desktop/6.0
- canonical/red hat enterprise linux server
- version/red hat enterprise linux server/6.0
- canonical/redhat enterprise linux workstation
- version/redhat enterprise linux workstation/6.0