Google Chrome up to 59 Blink HTML Page information disclosure

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Google Chrome up to 59. Affected by this vulnerability is an unknown functionality of the component Blink. Performing a manipulation as part of HTML Page results in information disclosure. This vulnerability is cataloged as CVE-2017-5075. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Google Chrome up to 59 (Web Browser). This affects an unknown functionality of the component Blink. The manipulation as part of a HTML Page leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

Inappropriate implementation in CSP reporting in Blink in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, allowed a remote attacker to obtain the value of url fragments via a crafted HTML page.

The bug was discovered 06/05/2017. The weakness was shared 10/27/2017 by Andrey Kovalev with Qihoo 360 Vulcan Team (Website). The advisory is shared at security.gentoo.org. This vulnerability is uniquely identified as CVE-2017-5075 since 01/02/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. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 37 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 101583 (Fedora 26 : qt5-qtwebengine (2017-1e34da27f3)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236369 (Red Hat Update for chromium-browser (RHSA-2017:1399)).

Upgrading to version 59.0.3071.86 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 (101583) and SecurityFocus (BID 98861†). The entries VDB-108663, VDB-108664, VDB-108665 and VDB-108666 are related to this item. 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: 4.3
VulDB Meta Temp Score: 4.2

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 4.3
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
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: 101583
Nessus Name: Fedora 26 : qt5-qtwebengine (2017-1e34da27f3)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 867773
OpenVAS Name: Fedora Update for chromium-native_client FEDORA-2017-b8d76bef4e
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 59.0.3071.86

Timelineinfo

01/02/2017 🔍
06/05/2017 +154 days 🔍
06/05/2017 +0 days 🔍
07/12/2017 +37 days 🔍
07/17/2017 +5 days 🔍
10/27/2017 +102 days 🔍
10/27/2017 +0 days 🔍
10/27/2017 +0 days 🔍
01/04/2023 +1895 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: FEDORA-2017-1e34da27f3
Researcher: Andrey Kovalev
Organization: Qihoo 360 Vulcan Team
Status: Not defined

CVE: CVE-2017-5075 (🔍)
GCVE (CVE): GCVE-0-2017-5075
GCVE (VulDB): GCVE-100-108669

OVAL: 🔍

SecurityFocus: 98861 - Google Chrome Prior to 59.0.3071.86 Multiple Security Vulnerabilities
SecurityTracker: 1038622

See also: 🔍

Entryinfo

Created: 10/27/2017 19:48
Updated: 01/04/2023 17:31
Changes: 10/27/2017 19:48 (82), 12/01/2019 08:45 (2), 01/20/2021 20:28 (2), 01/04/2023 17:24 (3), 01/04/2023 17:31 (1)
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 need the next level of professionalism?

Upgrade your account now!