Google Chrome up to 49 Navigation 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.
8.6$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Chrome up to 49. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the component Navigation. Performing a manipulation results in use after free. This vulnerability was named CVE-2016-1647. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, was found in Google Chrome up to 49 (Web Browser). This affects an unknown function of the component Navigation. The manipulation with an unknown input 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 weakness was presented 03/24/2016 with Zero Day Initiative as Stable Channel Update, March 2016 as confirmed release notes (Blog). It is possible to read the advisory at googlechromereleases.blogspot.com. This vulnerability is uniquely identified as CVE-2016-1647 since 01/12/2016. 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. 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 07/11/2022). 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 91176 (GLSA-201605-02 : Chromium: Multiple vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 196454 (Ubuntu Security Notification for Oxide-qt Vulnerabilities (USN-2955-1)).

Upgrading to version 49.0.2623.108 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (91176), SecurityFocus (BID 85457†), SecurityTracker (ID 1035423†) and Vulnerability Center (SBV-57735†). See VDB-81156, VDB-81157, VDB-81158 and VDB-81159 for similar entries. Be aware that VulDB is the high quality source 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: 8.8
VulDB Meta Temp Score: 8.6

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
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: 91176
Nessus Name: GLSA-201605-02 : Chromium: Multiple vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 800562
OpenVAS Name: Google Chrome Security Updates(stable-channel-update_24-2016-03)-Windows
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 49.0.2623.108

Timelineinfo

01/12/2016 🔍
03/24/2016 +72 days 🔍
03/24/2016 +0 days 🔍
03/24/2016 +0 days 🔍
03/24/2016 +0 days 🔍
03/25/2016 +1 days 🔍
03/26/2016 +1 days 🔍
03/29/2016 +2 days 🔍
03/29/2016 +0 days 🔍
05/17/2016 +49 days 🔍
07/11/2022 +2246 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update, March 2016
Organization: Zero Day Initiative
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-1647 (🔍)
GCVE (CVE): GCVE-0-2016-1647
GCVE (VulDB): GCVE-100-81543

OVAL: 🔍

SecurityFocus: 85457 - Google Chrome Prior to 49.0.2623.108 Multiple Security Vulnerabilities
SecurityTracker: 1035423
Vulnerability Center: 57735 - Google Chrome before 49.0.2623.108 Remote Unspecified Vulnerability Related to Use-after-free Read in Navigation, Medium

See also: 🔍

Entryinfo

Created: 03/29/2016 12:51
Updated: 07/11/2022 15:52
Changes: 03/29/2016 12:51 (80), 02/02/2019 11:41 (14), 07/11/2022 15:52 (3)
Complete: 🔍
Cache ID: 216:B90:103

Be aware that VulDB is the high quality source for vulnerability data.

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!