Google Chrome up to 51 Extensions information disclosure

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

Summaryinfo

A vulnerability classified as problematic has been found in Google Chrome up to 51. This affects an unknown function of the component Extensions. This manipulation causes information disclosure. This vulnerability is tracked as CVE-2016-1687. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 51 (Web Browser). It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component Extensions. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

The renderer implementation in Google Chrome before 51.0.2704.63 does not properly restrict public exposure of classes, which allows remote attackers to obtain sensitive information via vectors related to extensions.

The weakness was disclosed 05/25/2016 by Aleksandar Nikolic (OUSPG) with Cisco Talos as Stable Channel Update, May 2016 as confirmed release notes (Website). It is possible to read the advisory at googlechromereleases.blogspot.com. This vulnerability is known as CVE-2016-1687 since 01/12/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 91351 (Google Chrome < 51.0.2704.63 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 370005 (Google Chrome Prior to 51.0.2704.63 Multiple Vulnerabilities).

Upgrading to version 51.0.2704.63 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 (91351), SecurityFocus (BID 90876†) and SecurityTracker (ID 1035981†). The entries VDB-87298, VDB-87299, VDB-87300 and VDB-87301 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality 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: 5.9
VulDB Meta Temp Score: 5.8

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 91351
Nessus Name: Google Chrome < 51.0.2704.63 Multiple Vulnerabilities (Mac OS X)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 831745
OpenVAS Name: SuSE Update for Chromium openSUSE-SU-2016:1430-1 (Chromium)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Chrome 51.0.2704.63

Timelineinfo

01/12/2016 🔍
05/25/2016 +134 days 🔍
05/25/2016 +0 days 🔍
05/25/2016 +0 days 🔍
05/27/2016 +2 days 🔍
05/27/2016 +0 days 🔍
05/28/2016 +1 days 🔍
06/05/2016 +8 days 🔍
08/22/2022 +2269 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update, May 2016
Researcher: Aleksandar Nikolic (OUSPG)
Organization: Cisco Talos
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-1687 (🔍)
GCVE (CVE): GCVE-0-2016-1687
GCVE (VulDB): GCVE-100-87667

OVAL: 🔍

SecurityFocus: 90876 - Google Chrome Prior to 51.0.2704.63 Multiple Security Vulnerabilities
SecurityTracker: 1035981

See also: 🔍

Entryinfo

Created: 05/29/2016 00:31
Updated: 08/22/2022 14:28
Changes: 05/29/2016 00:31 (84), 12/20/2018 08:17 (7), 08/22/2022 14:28 (4)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality 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!