Google Chrome up to 58 Chrome Apps 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.2$5k-$25k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Google Chrome up to 58. Affected by this issue is some unknown functionality of the component Chrome Apps. The manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2017-5062. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 58 (Web Browser). It has been rated as critical. This issue affects some unknown functionality of the component Chrome Apps. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

A use after free in Chrome Apps in Google Chrome prior to 58.0.3029.81 for Mac, Windows, and Linux, and 58.0.3029.83 for Android, allowed a remote attacker to potentially perform out of bounds memory access via a crafted Chrome extension.

The bug was discovered 04/19/2017. The weakness was disclosed 04/19/2017 by Wadih Matar with Zero Day Initiative as Stable Channel Update for Desktop, April 2017 as confirmed news (Website). The advisory is shared at chromereleases.googleblog.com. The identification of this vulnerability is CVE-2017-5062 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. 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 09/17/2020). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability scanner Nessus provides a plugin with the ID 101504 (Fedora 25 : qt5-qtwebengine (2017-58cde32413)), 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 169947 (OpenSUSE Security Update for chromium (openSUSE-SU-2017:1098-1)).

Upgrading to version 58.0.3029.81 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (101504), SecurityFocus (BID 97939†) and SecurityTracker (ID 1038317†). The entries VDB-100276, VDB-100278, VDB-100279 and VDB-100280 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

Version

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: 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: 101504
Nessus Name: Fedora 25 : qt5-qtwebengine (2017-58cde32413)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 867773
OpenVAS Name: Fedora Update for chromium FEDORA-2017-dc7ce3b314
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Chrome 58.0.3029.81

Timelineinfo

01/02/2017 🔍
04/19/2017 +107 days 🔍
04/19/2017 +0 days 🔍
04/19/2017 +0 days 🔍
04/19/2017 +0 days 🔍
04/20/2017 +1 days 🔍
04/20/2017 +0 days 🔍
07/13/2017 +84 days 🔍
10/27/2017 +106 days 🔍
09/17/2020 +1056 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update for Desktop, April 2017
Researcher: Wadih Matar
Organization: Zero Day Initiative
Status: Confirmed

CVE: CVE-2017-5062 (🔍)
GCVE (CVE): GCVE-0-2017-5062
GCVE (VulDB): GCVE-100-100277

OVAL: 🔍

SecurityFocus: 97939 - Google Chrome Prior to 58.0.3029.81 Multiple Security Vulnerabilities
OSVDB: - CVE-2017-5062 - Google - Chrome - Use-After-Free Issue
SecurityTracker: 1038317

See also: 🔍

Entryinfo

Created: 04/20/2017 14:49
Updated: 09/17/2020 21:01
Changes: 04/20/2017 14:49 (89), 09/17/2020 21:01 (1)
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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!