Google Chrome up to 57 v8 HTML Page Memory information disclosure

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

Summaryinfo

A vulnerability was found in Google Chrome up to 57. It has been declared as problematic. This vulnerability affects unknown code of the component v8. The manipulation as part of HTML Page results in information disclosure (Memory). This vulnerability is cataloged as CVE-2017-5040. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 57 (Web Browser). It has been classified as problematic. Affected is some unknown processing of the component v8. The manipulation as part of a HTML Page leads to a information disclosure vulnerability (Memory). CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:

V8 in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android was missing a neutering check, which allowed a remote attacker to read values in memory via a crafted HTML page.

The bug was discovered 03/09/2017. The weakness was shared 04/24/2017 by Holger Fuhrmannek with Tencent (Website). The advisory is available at chromereleases.googleblog.com. This vulnerability is traded as CVE-2017-5040 since 01/02/2017. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.

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 best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.5
VulDB Meta Temp Score: 4.4

VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 4.3
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Name: Memory
Class: Information disclosure / Memory
CWE: CWE-200 / CWE-284 / CWE-266
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-5040 (🔍)
GCVE (CVE): GCVE-0-2017-5040
GCVE (VulDB): GCVE-100-100554

OVAL: 🔍

SecurityFocus: 96767 - Google Chrome Prior to 57.0.2987.98 Multiple Security Vulnerabilities
OSVDB: - CVE-2017-5040 - Google - Chrome - Information Disclosure Issue

See also: 🔍

Entryinfo

Created: 04/25/2017 09:00
Updated: 12/02/2022 09:32
Changes: 04/25/2017 09:00 (80), 09/20/2020 17:56 (8), 12/02/2022 09:32 (4)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!