CVE-2018-6109
published 2019-01-09CVE-2018-6109: 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…
PriorityP431medium6.5CVSS 3.0
AVNACLPRNUIRSUCHINAN
EPSS
1.41%
70.0th percentile
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.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| chrome | < 66.0.3359.117 | 66.0.3359.117 | |
| chrome | >= unspecified < 66.0.3359.117 | 66.0.3359.117 | |
| redhat | enterprise_linux_desktop | — | — |
| redhat | enterprise_linux_server | — | — |
| redhat | enterprise_linux_workstation | — | — |
CVSS provenance
nvdv3.06.5MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/A:N
osv6.5MEDIUM
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
chromium-browser: Incorrect handling of files by FileAPI
vendor_redhat·2018-04-17·CVSS 6.5
CVE-2018-6109 [MEDIUM] chromium-browser: Incorrect handling of files by FileAPI
chromium-browser: Incorrect handling of files by FileAPI
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.
GHSA
GHSA-pcp9-rq8r-pwrj: 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 prio
ghsa_unreviewed·2022-05-14
CVE-2018-6109 [MEDIUM] CWE-200 GHSA-pcp9-rq8r-pwrj: 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 prio
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.
OSV
CVE-2018-6109: 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 prio
osv·2019-01-09·CVSS 6.5
CVE-2018-6109 [MEDIUM] CVE-2018-6109: 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 prio
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.
No detection rules found.
No public exploits indexed.
Bugzilla
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-6094 CVE-2018-6095 CVE-2018-6096 CVE-2018-6097 CVE-2018-6098 CVE-
bugzilla·2018-04-18·CVSS 8.8
CVE-2018-6085 [HIGH] 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-6094 CVE-2018-6095 CVE-2018-6096 CVE-2018-6097 CVE-2018-6098 CVE-
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-6094 CVE-2018-6095 CVE-2018-6096 CVE-2018-6097 CVE-2018-6098 CVE-2018-6099 ... chromium: various flaws [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the releva
Bugzilla
CVE-2018-6109 chromium-browser: Incorrect handling of files by FileAPI
bugzilla·2018-04-18·CVSS 6.5
CVE-2018-6109 [MEDIUM] CVE-2018-6109 chromium-browser: Incorrect handling of files by FileAPI
CVE-2018-6109 chromium-browser: Incorrect handling of files by FileAPI
The following flaw was identified in the Chromium browser: Incorrect handling of files by FileAPI.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=710190
External References:
https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html
Discussion:
Created chromium tracking bugs for this issue:
Affects: fedora-all [bug 1568801]
Affects: epel-7 [bug 1568800]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2018:1195 https://access.redhat.com/errata/RHSA-2018:1195
Bugzilla
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-6094 CVE-2018-6095 CVE-2018-6096 CVE-2018-6097 CVE-2018-6098 CVE-
bugzilla·2018-04-18·CVSS 8.8
CVE-2018-6085 [HIGH] 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-6094 CVE-2018-6095 CVE-2018-6096 CVE-2018-6097 CVE-2018-6098 CVE-
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-6094 CVE-2018-6095 CVE-2018-6096 CVE-2018-6097 CVE-2018-6098 CVE-2018-6099 ... chromium: various flaws [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-l
http://www.securityfocus.com/bid/103917https://access.redhat.com/errata/RHSA-2018:1195https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.htmlhttps://crbug.com/710190https://security.gentoo.org/glsa/201804-22https://www.debian.org/security/2018/dsa-4182http://www.securityfocus.com/bid/103917https://access.redhat.com/errata/RHSA-2018:1195https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.htmlhttps://crbug.com/710190https://security.gentoo.org/glsa/201804-22https://www.debian.org/security/2018/dsa-4182
2019-01-09
Published