Google Chrome prior 65.0.3325.146 WebGL HTML Page memory corruption

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

Summaryinfo

A vulnerability, which was classified as critical, was found in Google Chrome. This issue affects some unknown processing of the component WebGL. Executing a manipulation as part of HTML Page can lead to memory corruption. This vulnerability is handled as CVE-2018-6073. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Google Chrome (Web Browser). This vulnerability affects some unknown functionality of the component WebGL. The manipulation as part of a HTML Page leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

A heap buffer overflow in WebGL in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page.

The bug was discovered 03/06/2018. The weakness was released 11/14/2018 by Abdulrahman Alqabandi (lokihardt) with Tencent (Website). The advisory is shared for download at chromereleases.googleblog.com. This vulnerability was named CVE-2018-6073 since 01/23/2018. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/06/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 107221 (Google Chrome < 65.0.3325.146 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 236674 (Red Hat Update for chromium-browser (RHSA-2018:0484)).

Upgrading to version 65.0.3325.146 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 (107221) and SecurityFocus (BID 103297†). Entries connected to this vulnerability are available at VDB-126842, VDB-126843, VDB-126844 and VDB-126845. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.4

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
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: 107221
Nessus Name: Google Chrome < 65.0.3325.146 Multiple Vulnerabilities (macOS)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 880848
OpenVAS Name: SuSE Update for Chromium openSUSE-SU-2018:0704-1 (Chromium)
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 65.0.3325.146

Timelineinfo

01/23/2018 🔍
03/06/2018 +42 days 🔍
03/06/2018 +0 days 🔍
03/06/2018 +0 days 🔍
03/08/2018 +2 days 🔍
11/14/2018 +251 days 🔍
11/14/2018 +0 days 🔍
11/15/2018 +1 days 🔍
06/06/2023 +1664 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

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

CVE: CVE-2018-6073 (🔍)
GCVE (CVE): GCVE-0-2018-6073
GCVE (VulDB): GCVE-100-126856

OVAL: 🔍

SecurityFocus: 103297 - Google Chrome Prior to 65.0.3325.146 Multiple Security Vulnerabilities

See also: 🔍

Entryinfo

Created: 11/15/2018 07:53
Updated: 06/06/2023 14:48
Changes: 11/15/2018 07:53 (77), 04/13/2020 07:42 (7), 06/06/2023 14:48 (4)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!