Google Chrome up to 50 Blink BindingSecurity.cpp input validation

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.2$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Chrome up to 50. It has been rated as critical. This affects an unknown function of the file BindingSecurity.cpp of the component Blink. Performing a manipulation results in input validation. This vulnerability is identified as CVE-2016-1661. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical has been found in Google Chrome up to 50 (Web Browser). This affects an unknown function of the file BindingSecurity.cpp of the component Blink. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Blink, as used in Google Chrome before 50.0.2661.94, does not ensure that frames satisfy a check for the same renderer process in addition to a Same Origin Policy check, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted web site, related to BindingSecurity.cpp and DOMWindow.cpp.

The weakness was released 05/14/2016 by Atte Kettunen with OUSPG (Website). The advisory is shared at crbug.com. This vulnerability is uniquely identified as CVE-2016-1661 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. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/19/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 90795 (Google Chrome < 50.0.2661.94 Multiple Vulnerabilities (Mac OS X)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family MacOS X Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 175732 (Debian Security Update for chromium-browser (DSA 3564-1)).

Upgrading to version 50.0.2661.94 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (90795) and SecurityFocus (BID 89106†). Entries connected to this vulnerability are available at VDB-87380, VDB-87382, VDB-87383 and VDB-87384. 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: 8.4
VulDB Meta Temp Score: 8.2

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.0
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Input validation
CWE: CWE-20
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: 90795
Nessus Name: Google Chrome < 50.0.2661.94 Multiple Vulnerabilities (Mac OS X)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 835123
OpenVAS Name: Google Chrome Security Updates(stable-channel-update_28-2016-04)-Linux
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 50.0.2661.94

Timelineinfo

01/12/2016 🔍
04/28/2016 +107 days 🔍
04/28/2016 +0 days 🔍
04/29/2016 +1 days 🔍
05/14/2016 +15 days 🔍
05/14/2016 +0 days 🔍
05/16/2016 +2 days 🔍
08/19/2022 +2286 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: RHSA-2016:0707
Researcher: Atte Kettunen
Organization: OUSPG
Status: Not defined
Confirmation: 🔍

CVE: CVE-2016-1661 (🔍)
GCVE (CVE): GCVE-0-2016-1661
GCVE (VulDB): GCVE-100-87381

OVAL: 🔍

SecurityFocus: 89106 - Google Chrome Prior to 50.0.2661.94 Multiple Security Vulnerabilities

See also: 🔍

Entryinfo

Created: 05/16/2016 09:39
Updated: 08/19/2022 11:36
Changes: 05/16/2016 09:39 (69), 11/26/2018 10:07 (15), 08/19/2022 11:36 (4)
Complete: 🔍
Cache ID: 216:5E9: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!