Google Chrome up to 52.0.2743 Blink improper authorization

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 classified as critical was found in Google Chrome up to 52.0.2743. Affected by this vulnerability is an unknown functionality of the component Blink. The manipulation leads to improper authorization. This vulnerability is known as CVE-2016-1711. The attack can be launched remotely. There is no exploit available. It is recommended to upgrade the affected component. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Detailsinfo

A vulnerability classified as critical has been found in Google Chrome up to 52.0.2743 (Web Browser). Affected is an unknown code of the component Blink. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was shared 07/20/2016 by Mariusz Mlynski (Cloudfuzzer) with Tencent as Stable Channel Update, July 2016 as confirmed release notes (Website). The advisory is available at googlechromereleases.blogspot.com. This vulnerability is traded as CVE-2016-1711 since 01/12/2016. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 09/09/2022). It is expected to see the exploit prices for this product increasing in the near future.This vulnerability is assigned to T1548.002 by the MITRE ATT&CK project.

The vulnerability scanner Nessus provides a plugin with the ID 92666 (Debian DSA-3637-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 370091 (Google Chrome Prior to 52.0.2743.82 Multiple Vulnerabilities).

Upgrading to version 52.0.2743.82 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 release notes contains the following remark:

This update includes 48 security fixes.

The vulnerability is also documented in the databases at Tenable (92666) and SecurityFocus (BID 92053†). The entries VDB-90229, VDB-90230, VDB-90231 and VDB-90232 are related to this item. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

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: Improper authorization
CWE: CWE-285 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

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

OpenVAS ID: 855646
OpenVAS Name: SuSE Update for Chromium openSUSE-SU-2016:1869-1 (Chromium)
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 52.0.2743.82

Timelineinfo

01/12/2016 🔍
07/20/2016 +190 days 🔍
07/20/2016 +0 days 🔍
07/20/2016 +0 days 🔍
07/23/2016 +3 days 🔍
07/23/2016 +0 days 🔍
08/02/2016 +10 days 🔍
09/09/2022 +2229 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

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

CVE: CVE-2016-1711 (🔍)
GCVE (CVE): GCVE-0-2016-1711
GCVE (VulDB): GCVE-100-90234

OVAL: 🔍

SecurityFocus: 92053 - Google Chrome Prior to 52.0.2743.82 Multiple Security Vulnerabilities
SecurityTracker: 1036428

See also: 🔍

Entryinfo

Created: 07/23/2016 12:08 PM
Updated: 09/09/2022 09:50 AM
Changes: 07/23/2016 12:08 PM (74), 03/07/2019 03:30 PM (14), 09/09/2022 09:50 AM (4)
Complete: 🔍
Cache ID: 18:3CC:40

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!