Google Chrome up to 57 on Windows/Mac Certificate race condition

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Google Chrome up to 57 on Windows/Mac. This impacts an unknown function of the component Certificate Handler. This manipulation causes race condition. The identification of this vulnerability is CVE-2017-5035. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Google Chrome up to 57 on Windows/Mac (Web Browser). Affected by this vulnerability is an unknown functionality of the component Certificate Handler. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Google Chrome prior to 57.0.2987.98 for Windows and Mac had a race condition, which could cause Chrome to display incorrect certificate information for a site.

The bug was discovered 03/09/2017. The weakness was shared 04/24/2017 by Holger Fuhrmannek with Tencent (Website). The advisory is shared at chromereleases.googleblog.com. This vulnerability is known as CVE-2017-5035 since 01/02/2017. 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 vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 97783 (Debian DSA-3810-1 : chromium-browser - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236287 (Red Hat Update for chromium-browser Security (RHSA-2017:0499)).

Upgrading to version 57.0.2987.98 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 (97783) and SecurityFocus (BID 96767†). The entries VDB-99042, VDB-100544, VDB-100545 and VDB-100546 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: 7.6
VulDB Meta Temp Score: 7.4

VulDB Base Score: 7.1
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.1
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
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: 97783
Nessus Name: Debian DSA-3810-1 : chromium-browser - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 703810
OpenVAS Name: Debian Security Advisory DSA 3810-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 57.0.2987.98

Timelineinfo

01/02/2017 🔍
03/09/2017 +66 days 🔍
03/09/2017 +0 days 🔍
03/15/2017 +6 days 🔍
03/17/2017 +2 days 🔍
04/24/2017 +38 days 🔍
04/24/2017 +0 days 🔍
04/25/2017 +1 days 🔍
12/02/2022 +2047 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: RHSA-2017:0499
Researcher: Holger Fuhrmannek
Organization: Tencent
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-5035 (🔍)
GCVE (CVE): GCVE-0-2017-5035
GCVE (VulDB): GCVE-100-100549

OVAL: 🔍

SecurityFocus: 96767 - Google Chrome Prior to 57.0.2987.98 Multiple Security Vulnerabilities
OSVDB: - CVE-2017-5035 - Google - Chrome - Default Configuration Issue

See also: 🔍

Entryinfo

Created: 04/25/2017 08:58
Updated: 12/02/2022 09:20
Changes: 04/25/2017 08:58 (79), 09/20/2020 17:02 (8), 12/02/2022 09:20 (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 ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!