Google Chrome prior 62.0.3202.62 Skia HTML Page 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.4$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Chrome. It has been classified as critical. This impacts an unknown function of the component Skia. This manipulation as part of HTML Page causes memory corruption. This vulnerability is tracked as CVE-2017-5125. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Google Chrome (Web Browser). It has been declared as critical. Affected by this vulnerability is an unknown code block of the component Skia. The manipulation as part of a HTML Page leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Heap buffer overflow in Skia in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

The bug was discovered 10/17/2017. The weakness was disclosed 02/07/2018 by Kushal Arvind Shah (xisigr) with Fortinet's FortiGuard Labs (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2017-5125 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 price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/06/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 4 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 104063 (FreeBSD : chromium -- multiple vulnerabilities (a692bffe-b6ad-11e7-a1c2-e8e0b747a45a)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236535 (Red Hat Update for chromium-browser (RHSA-2017:2997)).

Upgrading to version 62.0.3202.62 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 (104063) and SecurityFocus (BID 101482†). The entries VDB-112940, VDB-112941, VDB-112942 and VDB-112943 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

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: 104063
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (a692bffe-b6ad-11e7-a1c2-e8e0b747a45a)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

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

Timelineinfo

01/02/2017 🔍
10/17/2017 +288 days 🔍
10/18/2017 +1 days 🔍
10/21/2017 +3 days 🔍
10/23/2017 +2 days 🔍
02/07/2018 +107 days 🔍
02/07/2018 +0 days 🔍
02/08/2018 +1 days 🔍
02/06/2023 +1824 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: RHSA-2017:2997⛔
Researcher: Kushal Arvind Shah (xisigr)
Organization: Fortinet's FortiGuard Labs
Status: Not defined

CVE: CVE-2017-5125 (🔍)
GCVE (CVE): GCVE-0-2017-5125
GCVE (VulDB): GCVE-100-112957

OVAL: 🔍

SecurityFocus: 101482 - Google Chrome Prior to 62.0.3202.62 Multiple Security Vulnerabilities

See also: 🔍

Entryinfo

Created: 02/08/2018 07:01
Updated: 02/06/2023 07:53
Changes: 02/08/2018 07:01 (77), 01/02/2020 15:45 (7), 02/06/2023 07:53 (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 ▸

Do you know our Splunk app?

Download it now for free!