Google Chrome up to 52.x Shared Worker input validation

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.
6.2$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Google Chrome up to 52.x. Affected by this issue is some unknown functionality of the component Shared Worker. The manipulation leads to input validation. This vulnerability is handled as CVE-2018-6032. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Detailsinfo

A vulnerability classified as critical was found in Google Chrome up to 52.x (Web Browser). Affected by this vulnerability is some unknown functionality of the component Shared Worker. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Insufficient policy enforcement in Blink in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potentially leak user cross-origin data via a crafted HTML page.

The bug was discovered 01/24/2018. The weakness was published 01/24/2018 by Masato Kinugawa (Paul) with Tencent (Website). It is possible to read the advisory at chromereleases.googleblog.com. This vulnerability is known as CVE-2018-6032 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. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/03/2023). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability scanner Nessus provides a plugin with the ID 106486 (Google Chrome < 64.0.3282.119 Multiple Vulnerabilities (macOS)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family MacOS X Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236634 (Red Hat Update for chromium-browser (RHSA-2018:0265)).

Upgrading to version 53.0 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (106486), SecurityFocus (BID 102797†) and SecurityTracker (ID 1040282†). Similar entries are available at VDB-112550, VDB-112551, VDB-112552 and VDB-112553. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: Input validation
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Nessus ID: 106486
Nessus Name: Google Chrome < 64.0.3282.119 Multiple Vulnerabilities (macOS)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 864007
OpenVAS Name: Google Chrome Security Updates(stable-channel-update-for-desktop_24-2018-01)-Linux
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Chrome 53.0

Timelineinfo

01/23/2018 🔍
01/24/2018 +1 days 🔍
01/24/2018 +0 days 🔍
01/24/2018 +0 days 🔍
01/24/2018 +0 days 🔍
01/25/2018 +1 days 🔍
01/28/2018 +3 days 🔍
01/30/2018 +2 days 🔍
09/25/2018 +237 days 🔍
02/03/2023 +1592 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: RHSA-2018:0265
Researcher: Masato Kinugawa (Paul)
Organization: Tencent
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2018-6032 (🔍)
GCVE (CVE): GCVE-0-2018-6032
GCVE (VulDB): GCVE-100-112555

OVAL: 🔍

SecurityFocus: 102797 - Google Chrome Multiple Security Vulnerabilities
SecurityTracker: 1040282

See also: 🔍

Entryinfo

Created: 01/28/2018 10:38
Updated: 02/03/2023 07:16
Changes: 01/28/2018 10:38 (78), 12/30/2019 15:22 (11), 02/03/2023 07:16 (4)
Complete: 🔍
Cache ID: 216:04C:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!