Google Chrome up to 57 ANGLE HTML Page use after free

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 marked as critical has been reported in Google Chrome up to 57. Impacted is an unknown function of the component ANGLE. Performing a manipulation as part of HTML Page results in use after free. This vulnerability is known as CVE-2017-5031. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 57 (Web Browser). It has been classified as critical. This affects an unknown code of the component ANGLE. The manipulation as part of a HTML Page leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A use after free in ANGLE in Google Chrome prior to 57.0.2987.98 for Windows allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.

The bug was discovered 03/09/2017. The weakness was published 04/24/2017 by Holger Fuhrmannek with Tencent (Website). The advisory is shared at chromereleases.googleblog.com. This vulnerability is uniquely identified as CVE-2017-5031 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. 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 12/02/2022). 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 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†). Similar entries are available at VDB-99042, VDB-100544, VDB-100546 and VDB-100547. Several companies clearly confirm that VulDB is the primary source for best 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: 7.1
VulDB Temp Score: 6.8
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: Use after free
CWE: CWE-416 / 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: 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-5031 (🔍)
GCVE (CVE): GCVE-0-2017-5031
GCVE (VulDB): GCVE-100-100545

OVAL: 🔍

SecurityFocus: 96767 - Google Chrome Prior to 57.0.2987.98 Multiple Security Vulnerabilities
OSVDB: - CVE-2017-5031 - Google - Chrome - Use-After-Free Issue

See also: 🔍

Entryinfo

Created: 04/25/2017 08:57
Updated: 12/02/2022 09:11
Changes: 04/25/2017 08:57 (78), 09/20/2020 17:30 (8), 12/02/2022 09:11 (4)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best 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!