Google Chrome up to 54 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.
6.3$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Google Chrome up to 54. Affected by this vulnerability is an unknown functionality of the component Extensions. This manipulation causes information disclosure. This vulnerability is tracked as CVE-2016-5201. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Google Chrome up to 54 (Web Browser) and classified as critical. Affected by this vulnerability is an unknown functionality 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:

A leak of privateClass in the extensions API in Google Chrome prior to 54.0.2840.100 for Linux, and 54.0.2840.99 for Windows, and 54.0.2840.98 for Mac allowed a remote attacker to access privileged JavaScript code via a crafted HTML page.

The bug was discovered 11/09/2016. The weakness was disclosed 11/09/2016 by Rob Wu (Paul) with Google as Stable Channel Update for Desktop, November 2016 as confirmed release notes (Blog). The advisory is shared at googlechromereleases.blogspot.com. The public release has been coordinated in cooperation with Google. This vulnerability is known as CVE-2016-5201 since 05/31/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 94677 (Google Chrome < 54.0.2840.98 Multiple Vulnerabilities (macOS)), 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 236190 (Red Hat Update for chromium-browser (RHSA-2016:2718)).

Upgrading to version 54.0.2840.98, 54.0.2840.99 or 54.0.2840.100 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 (94677), SecurityFocus (BID 94196†) and SecurityTracker (ID 1037273†). The entries VDB-93575, VDB-93576 and VDB-93578 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best 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: 6.5
VulDB Meta Temp Score: 6.3

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
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: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 94677
Nessus Name: Google Chrome < 54.0.2840.98 Multiple Vulnerabilities (macOS)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 855379
OpenVAS Name: Google Chrome Security Updates(stable-channel-update-for-desktop_9-2016-11)-Linux
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 54.0.2840.98/54.0.2840.99/54.0.2840.100

Timelineinfo

05/31/2016 🔍
11/09/2016 +162 days 🔍
11/09/2016 +0 days 🔍
11/09/2016 +0 days 🔍
11/09/2016 +0 days 🔍
11/10/2016 +1 days 🔍
11/11/2016 +1 days 🔍
11/11/2016 +0 days 🔍
01/19/2017 +69 days 🔍
05/14/2026 +3401 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update for Desktop, November 2016
Researcher: Rob Wu (Paul)
Organization: Google
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2016-5201 (🔍)
GCVE (CVE): GCVE-0-2016-5201
GCVE (VulDB): GCVE-100-93577

OVAL: 🔍

SecurityFocus: 94196 - Google Chrome Multiple Security Vulnerabilities
SecurityTracker: 1037273

See also: 🔍

Entryinfo

Created: 11/11/2016 16:26
Updated: 05/14/2026 00:50
Changes: 11/11/2016 16:26 (78), 05/30/2019 09:49 (15), 05/14/2026 00:50 (17)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!