Google Chrome prior 66.0.3359.106 Networking Disk Cache HTML Page use after free

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 was found in Google Chrome. It has been rated as critical. This impacts an unknown function of the component Networking Disk Cache. This manipulation as part of HTML Page causes use after free. This vulnerability is tracked as CVE-2018-6086. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical was found in Google Chrome (Web Browser). Affected by this vulnerability is an unknown function of the component Networking Disk Cache. The manipulation as part of a HTML Page leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

A double-eviction in the Incognito mode cache that lead to a user-after-free in Networking Disk Cache in Google Chrome prior to 66.0.3359.106 allowed a remote attacker to execute arbitrary code via a crafted HTML page.

The bug was discovered 04/17/2018. The weakness was disclosed 12/04/2018 by Abdulrahman Alqabandi (lokihardt) with Tencent (Website). The advisory is shared at chromereleases.googleblog.com. This vulnerability is known as CVE-2018-6086 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. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/12/2023). It is expected to see the exploit prices for this product increasing in the near future.

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 370889 (Google Chrome Prior to 66.0.3359.117 Multiple Vulnerabilities).

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

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

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: Use after free
CWE: CWE-416 / 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: 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.106

Timelineinfo

01/23/2018 🔍
04/17/2018 +84 days 🔍
04/17/2018 +0 days 🔍
04/24/2018 +7 days 🔍
04/24/2018 +0 days 🔍
12/04/2018 +224 days 🔍
12/04/2018 +0 days 🔍
12/05/2018 +1 days 🔍
06/12/2023 +1650 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-6086 (🔍)
GCVE (CVE): GCVE-0-2018-6086
GCVE (VulDB): GCVE-100-127477

OVAL: 🔍

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

See also: 🔍

Entryinfo

Created: 12/05/2018 08:18
Updated: 06/12/2023 17:48
Changes: 12/05/2018 08:18 (79), 04/17/2020 12:02 (7), 06/12/2023 17:48 (4)
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 want to use VulDB in your project?

Use the official API to access entries easily!