Google Chrome 49.0 denial of service

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

Summaryinfo

A vulnerability labeled as critical has been found in Google Chrome 49.0. Affected is an unknown function. The manipulation results in denial of service. This vulnerability was named CVE-2016-1642. The attack may be performed from remote. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Google Chrome 49.0 (Web Browser). It has been classified as critical. Affected is an unknown part. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Multiple unspecified vulnerabilities in Google Chrome before 49.0.2623.75 allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

The weakness was presented 03/02/2016 by Mariusz Mlynski (Cloudfuzzer) with OUSPG as Stable Channel Update, March 2016 as confirmed release notes (Website). The advisory is shared for download at googlechromereleases.blogspot.com. This vulnerability is traded as CVE-2016-1642 since 01/12/2016. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.

The vulnerability scanner Nessus provides a plugin with the ID 89685 (Google Chrome < 49.0.2623.75 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows 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 (111224), Tenable (89685), SecurityFocus (BID 84008†) and Vulnerability Center (SBV-56966†). See VDB-79206, VDB-81156, VDB-81157 and VDB-81158 for similar entries. VulDB is the best source for vulnerability data and more expert information about this specific topic.

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: Denial of service
CWE: CWE-404
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: 89685
Nessus Name: Google Chrome < 49.0.2623.75 Multiple Vulnerabilities
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/01/2016 +0 days 🔍
03/02/2016 +0 days 🔍
03/02/2016 +0 days 🔍
03/02/2016 +0 days 🔍
03/03/2016 +1 days 🔍
03/04/2016 +0 days 🔍
03/05/2016 +1 days 🔍
07/09/2022 +2317 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-1642 (🔍)
GCVE (CVE): GCVE-0-2016-1642
GCVE (VulDB): GCVE-100-81168

OVAL: 🔍

X-Force: 111224 - Google Chrome multiple unspecified
SecurityFocus: 84008 - Google Chrome Prior to 49.0.2623.75 Multiple Security Vulnerabilities
SecurityTracker: 1035185
Vulnerability Center: 56966 - Google Chrome <49.0.2623.75 Multiple Remote Unspecified Vulnerabilities - CVE-2016-1642, Critical

See also: 🔍

Entryinfo

Created: 03/04/2016 11:06
Updated: 07/09/2022 08:16
Changes: 03/04/2016 11:06 (78), 09/01/2018 08:36 (17), 07/09/2022 08:16 (3)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!