Google Chrome up to 61 on Windows v8 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 up to 61 on Windows and classified as critical. This issue affects some unknown processing of the component v8. The manipulation as part of HTML Page leads to memory corruption. The identification of this vulnerability is CVE-2017-5122. The attack may be initiated remotely. There is no exploit available. It is recommended to upgrade the affected component. Once again VulDB remains the best source for vulnerability data.

Detailsinfo

A vulnerability has been found in Google Chrome up to 61 on Windows (Web Browser) and classified as critical. This vulnerability affects an unknown part of the component v8. 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. CVE summarizes:

Inappropriate use of table size handling in V8 in Google Chrome prior to 61.0.3163.100 for Windows allowed a remote attacker to trigger out-of-bounds access via a crafted HTML page.

The bug was discovered 09/21/2017. The weakness was released 10/27/2017 (Website). The advisory is available at security.gentoo.org. This vulnerability was named CVE-2017-5122 since 01/02/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 01/05/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 7 days. During that time the estimated underground price was around $25k-$100k. 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 370566 (Google Chrome Prior to 61.0.3163.100 Multiple Vulnerabilities).

Upgrading to version 61.0.3163.100 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 (103539) and SecurityFocus (BID 100947†). Entries connected to this vulnerability are available at VDB-106309, VDB-106310, VDB-106311 and VDB-106312. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
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: 🔍

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: 800562
OpenVAS Name: Google Chrome Security Updates(stable-channel-update-for-desktop_21-2017-09)-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 61.0.3163.100

Timelineinfo

01/02/2017 🔍
09/21/2017 +261 days 🔍
09/21/2017 +0 days 🔍
09/28/2017 +7 days 🔍
09/29/2017 +1 days 🔍
10/27/2017 +28 days 🔍
10/27/2017 +0 days 🔍
10/27/2017 +0 days 🔍
01/05/2023 +1896 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: RHSA-2017:2792
Researcher: Jordan Rabet
Status: Not defined

CVE: CVE-2017-5122 (🔍)
GCVE (CVE): GCVE-0-2017-5122
GCVE (VulDB): GCVE-100-108706

OVAL: 🔍

SecurityFocus: 100947
SecurityTracker: 1039497

See also: 🔍

Entryinfo

Created: 10/27/2017 08:05 PM
Updated: 01/05/2023 08:47 AM
Changes: 10/27/2017 08:05 PM (78), 12/01/2019 12:03 PM (2), 01/20/2021 09:58 PM (2), 01/20/2021 10:02 PM (3), 01/05/2023 08:47 AM (3)
Complete: 🔍
Cache ID: 18:970:40

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!