Google Chrome up to 52.x Omnibox URL 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 marked as critical has been reported in Google Chrome up to 52.x. Impacted is an unknown function of the component Omnibox. Performing a manipulation results in input validation (URL). This vulnerability is reported as CVE-2017-15420. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Google Chrome up to 52.x (Web Browser). This affects an unknown code of the component Omnibox. The manipulation with an unknown input leads to a input validation vulnerability (URL). CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Inappropriate implementation in browser navigation in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.

The bug was discovered 12/06/2017. The weakness was disclosed 01/24/2018 (Website). The advisory is shared at chromereleases.googleblog.com. This vulnerability is uniquely identified as CVE-2017-15420 since 10/17/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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 02/03/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 49 days. During that time the estimated underground price was around $25k-$100k. 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 370678 (Google Chrome Prior to 63.0.3239.84 Multiple Vulnerabilities).

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 100914†) and SecurityTracker (ID 1040282†). The entries VDB-106612, VDB-107426, VDB-109008 and VDB-112550 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

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: URL
Class: Input validation / URL
CWE: CWE-20
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: 106486
Nessus Name: Google Chrome < 64.0.3282.119 Multiple Vulnerabilities (macOS)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 862004
OpenVAS Name: Google Chrome Security Updates(stable-channel-update-for-desktop-2017-12)-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

09/13/2017 🔍
10/17/2017 +34 days 🔍
12/06/2017 +50 days 🔍
01/24/2018 +49 days 🔍
01/24/2018 +0 days 🔍
01/25/2018 +1 days 🔍
01/28/2018 +3 days 🔍
01/30/2018 +2 days 🔍
08/28/2018 +209 days 🔍
02/03/2023 +1620 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: RHSA-2017:3401
Researcher: Otto Airamo, Antti Levomäki.
Status: Confirmed

CVE: CVE-2017-15420 (🔍)
GCVE (CVE): GCVE-0-2017-15420
GCVE (VulDB): GCVE-100-112557

OVAL: 🔍

SecurityFocus: 100914 - Tcpdump CVE-2017-12997 Denial of Service Vulnerability
SecurityTracker: 1040282

See also: 🔍

Entryinfo

Created: 01/28/2018 10:38
Updated: 02/03/2023 07:27
Changes: 01/28/2018 10:38 (80), 12/30/2019 15:25 (7), 02/02/2021 07:15 (3), 02/03/2023 07:27 (3)
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 ▸

Interested in the pricing of exploits?

See the underground prices here!