Google Chrome up to 65.0.3325.146 URL Formatter Domain Name data processing

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$0-$5k0.00

Summaryinfo

A vulnerability categorized as critical has been discovered in Google Chrome. This affects an unknown part of the component URL Formatter. Executing a manipulation can lead to data processing (Domain Name). This vulnerability is tracked as CVE-2018-6107. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome (Web Browser). It has been declared as critical. This vulnerability affects an unknown functionality of the component URL Formatter. The manipulation with an unknown input leads to a data processing vulnerability (Domain Name). The CWE definition for the vulnerability is CWE-19. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Incorrect handling of confusable characters in URL Formatter in Google Chrome prior to 66.0.3359.106 allowed a remote attacker to perform domain spoofing via IDN homographs via a crafted domain name.

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 for download at chromereleases.googleblog.com. This vulnerability was named CVE-2018-6107 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 $0-$5k (estimation calculated on 07/19/2024). 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 277397 (Fedora Security Update for chromium (FEDORA-2018-94e1bc8c23)).

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-127477, VDB-127478 and VDB-127479 are pretty similar. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

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

Name: Domain Name
Class: Data processing / Domain Name
CWE: CWE-19
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 🔍
07/19/2024 +2053 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-6107 (🔍)
GCVE (CVE): GCVE-0-2018-6107
GCVE (VulDB): GCVE-100-127492

OVAL: 🔍

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

See also: 🔍

Entryinfo

Created: 12/05/2018 08:24
Updated: 07/19/2024 04:45
Changes: 12/05/2018 08:24 (77), 04/17/2020 14:22 (7), 06/13/2023 07:57 (4), 07/19/2024 04:45 (17)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!