Google Chrome 49.0 Blink 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.
9.1$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Google Chrome 49.0. Affected by this issue is some unknown functionality of the component Blink. Performing a manipulation results in use after free. This vulnerability is cataloged as CVE-2016-1633. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome 49.0 (Web Browser). It has been classified as critical. This affects an unknown functionality of the component Blink. 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 summary by CVE is:

Use-after-free vulnerability in Blink, as used in Google Chrome before 49.0.2623.75, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.

The weakness was shared 03/02/2016 by Mariusz Mlynski (Cloudfuzzer) with OUSPG as Stable Channel Update, March 2016 as confirmed release notes (Website). It is possible to read the advisory at googlechromereleases.blogspot.com. This vulnerability is uniquely identified as CVE-2016-1633 since 01/12/2016. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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/09/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 89697 (Debian DSA-3507-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 168634 (OpenSuSE Security Update for Security Chromium (openSUSE-SU-2016:0664-1)).

Upgrading to version 49.0.2623.75 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 X-Force (111215), Tenable (89697) and SecurityFocus (BID 84008†). The entries VDB-79206, VDB-81156, VDB-81157 and VDB-81158 are related to this item. 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: 9.8
VulDB Meta Temp Score: 9.1

VulDB Base Score: 9.8
VulDB Temp Score: 8.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.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: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 89697
Nessus Name: Debian DSA-3507-1 : chromium-browser - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 801855
OpenVAS Name: Google Chrome Multiple Vulnerabilities Mar16 (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.75

Timelineinfo

01/12/2016 🔍
03/01/2016 +49 days 🔍
03/02/2016 +0 days 🔍
03/02/2016 +0 days 🔍
03/04/2016 +2 days 🔍
03/05/2016 +1 days 🔍
03/06/2016 +1 days 🔍
07/09/2022 +2315 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update, March 2016
Researcher: Mariusz Mlynski (Cloudfuzzer)
Organization: OUSPG
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-1633 (🔍)
GCVE (CVE): GCVE-0-2016-1633
GCVE (VulDB): GCVE-100-81159

OVAL: 🔍

X-Force: 111215 - Google Chrome Blink code execution
SecurityFocus: 84008 - Google Chrome Prior to 49.0.2623.75 Multiple Security Vulnerabilities
SecurityTracker: 1035185

See also: 🔍

Entryinfo

Created: 03/04/2016 11:03
Updated: 07/09/2022 07:33
Changes: 03/04/2016 11:03 (63), 08/26/2018 09:28 (26), 07/09/2022 07:33 (3)
Complete: 🔍
Cache ID: 216::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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!