Google Chrome up to 66.0.3359.106 File API readAsText HTML Page information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Google Chrome. Affected is the function readAsText of the component File API. This manipulation as part of HTML Page causes information disclosure. This vulnerability is handled as CVE-2018-6109. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome (Web Browser). It has been declared as problematic. Affected by this vulnerability is the function readAsText of the component File API. The manipulation as part of a HTML Page leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

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.

The bug was discovered 04/17/2018. The weakness was released 01/09/2019 by Abdulrahman Alqabandi (lokihardt) with Tencent (Website). The advisory is shared at debian.org. This vulnerability is known as CVE-2018-6109 since 01/23/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 7 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 109290 (GLSA-201804-22 : Chromium, Google Chrome: Multiple vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 277397 (Fedora Security Update for chromium (FEDORA-2018-94e1bc8c23)).

Upgrading to version 66.0.3359.117 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (109290) and SecurityFocus (BID 103917†). Entries connected to this vulnerability are available at VDB-127476, VDB-127477, VDB-127478 and VDB-127479. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.3

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 109290
Nessus Name: GLSA-201804-22 : Chromium, Google Chrome: Multiple vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 56832
OpenVAS Name: Debian Security Advisory DSA 4182-1 (chromium-browser - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Chrome 66.0.3359.117

Timelineinfo

01/23/2018 🔍
04/17/2018 +84 days 🔍
04/17/2018 +0 days 🔍
04/24/2018 +7 days 🔍
04/24/2018 +0 days 🔍
01/09/2019 +260 days 🔍
01/09/2019 +0 days 🔍
01/10/2019 +1 days 🔍
07/19/2024 +2017 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: RHSA-2018:1195
Researcher: Abdulrahman Alqabandi (lokihardt)
Organization: Tencent
Status: Not defined
Confirmation: 🔍

CVE: CVE-2018-6109 (🔍)
GCVE (CVE): GCVE-0-2018-6109
GCVE (VulDB): GCVE-100-128941

OVAL: 🔍

SecurityFocus: 103917 - Google Chrome Prior to 66.0.3359.117 Multiple Security Vulnerabilities

See also: 🔍

Entryinfo

Created: 01/10/2019 21:22
Updated: 07/19/2024 07:07
Changes: 01/10/2019 21:22 (80), 04/28/2020 08:19 (6), 06/23/2023 15:47 (4), 07/19/2024 07:07 (17)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!