Google Chrome prior 61.0.3163.79 Skia memory corruption

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.2$5k-$25k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Google Chrome. The impacted element is an unknown function of the component Skia. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2017-5113. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Google Chrome (Web Browser). This affects some unknown functionality of the component Skia. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Math overflow in Skia in Google Chrome prior to 61.0.3163.79 for Mac, Windows, and Linux, and 61.0.3163.81 for Android, allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

The bug was discovered 09/05/2017. The weakness was released 09/05/2017 by Wenxu Wu as Stable Channel Update for Desktop, September 2017 as confirmed release notes (Website). It is possible to read the advisory at chromereleases.googleblog.com. This vulnerability is uniquely identified as CVE-2017-5113 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. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/14/2019). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability scanner Nessus provides a plugin with the ID 103539 (Debian DSA-3985-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 370546 (Google Chrome Prior to 61.0.3163.79 Multiple Vulnerabilities).

Upgrading to version 61.0.3163.79 eliminates this vulnerability. A possible mitigation has been published 4 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (103539), SecurityFocus (BID 100610†) and SecurityTracker (ID 1039291†). Entries connected to this vulnerability are available at VDB-106309, VDB-106310, VDB-106312 and VDB-106313. Be aware that VulDB is the high quality source for vulnerability data.

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: Memory corruption
CWE: 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: 103539
Nessus Name: Debian DSA-3985-1 : chromium-browser - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 53754
OpenVAS Name: Debian Security Advisory DSA 3985-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: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Chrome 61.0.3163.79

Timelineinfo

01/02/2017 🔍
09/05/2017 +246 days 🔍
09/05/2017 +0 days 🔍
09/05/2017 +0 days 🔍
09/07/2017 +2 days 🔍
09/10/2017 +3 days 🔍
09/28/2017 +18 days 🔍
09/29/2017 +1 days 🔍
10/27/2017 +28 days 🔍
11/14/2019 +748 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update for Desktop, September 2017
Researcher: Wenxu Wu
Status: Confirmed

CVE: CVE-2017-5113 (🔍)
GCVE (CVE): GCVE-0-2017-5113
GCVE (VulDB): GCVE-100-106311

OVAL: 🔍

SecurityFocus: 100610 - Google Chrome Prior to 61.0.3163.79 Multiple Security Vulnerabilities
SecurityTracker: 1039291

See also: 🔍

Entryinfo

Created: 09/10/2017 10:27
Updated: 11/14/2019 10:36
Changes: 09/10/2017 10:27 (76), 11/14/2019 10:36 (12)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!