Google Chrome up to 57 v8 HTML Page access control

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

Summaryinfo

A vulnerability was found in Google Chrome up to 57. It has been classified as critical. Affected by this issue is some unknown functionality of the component v8. The manipulation as part of HTML Page leads to access control. This vulnerability is traded as CVE-2017-5053. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Google Chrome up to 57 (Web Browser). This issue affects an unknown code block of the component v8. The manipulation as part of a HTML Page leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

An out-of-bounds read in V8 in Google Chrome prior to 57.0.2987.133 for Linux, Windows, and Mac, and 57.0.2987.132 for Android, allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page, related to Array.prototype.indexOf.

The bug was discovered 03/29/2017. The weakness was shared 10/27/2017 by Jeonghoon Shin with Zimperium zLabs (Website). It is possible to read the advisory at security.gentoo.org. The identification of this vulnerability is CVE-2017-5053 since 01/02/2017. The attack may be initiated remotely. No form of authentication is needed for a successful 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 01/04/2023). It is expected to see the exploit prices for this product increasing in the near future.The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 16 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 101624 (Fedora 26 : chromium (2017-49f828d4b1)), 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 236313 (Red Hat Update for chromium-browser Security (RHSA-2017:0860)).

Upgrading to version 57.0.2987.133 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 (101624) and SecurityFocus (BID 97220†). The entries VDB-108658, VDB-108660, VDB-108661 and VDB-108662 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.9
VulDB Meta Temp Score: 7.8

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.6
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
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: 101624
Nessus Name: Fedora 26 : chromium (2017-49f828d4b1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 867773
OpenVAS Name: Fedora Update for chromium FEDORA-2017-ff6940bf63
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.133

Timelineinfo

01/02/2017 🔍
03/29/2017 +86 days 🔍
03/29/2017 +0 days 🔍
04/14/2017 +16 days 🔍
07/17/2017 +94 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-49f828d4b1
Researcher: Jeonghoon Shin
Organization: Zimperium zLabs
Status: Not defined

CVE: CVE-2017-5053 (🔍)
GCVE (CVE): GCVE-0-2017-5053
GCVE (VulDB): GCVE-100-108659

OVAL: 🔍

SecurityFocus: 97220 - Google Chrome and Chrome OS Multiple Security Vulnerabilities

See also: 🔍

Entryinfo

Created: 10/27/2017 19:44
Updated: 01/04/2023 15:37
Changes: 10/27/2017 19:44 (82), 12/01/2019 08:18 (2), 01/04/2023 15:31 (4), 01/04/2023 15:37 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality 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!