Google Chrome up to 52 Extension code injection

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 marked as critical has been reported in Google Chrome up to 52. The affected element is an unknown function of the component Extension Handler. Performing a manipulation results in code injection. This vulnerability was named CVE-2016-5149. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Google Chrome up to 52 (Web Browser). This affects an unknown code of the component Extension Handler. The manipulation with an unknown input leads to a code injection vulnerability. CWE is classifying the issue as CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was presented 08/31/2016 by Nicolas Golubovic (OUSPG) with Zero Day Initiative as Stable Channel Update for Desktop, August 2016 as confirmed blog post (Website). The advisory is shared at googlechromereleases.blogspot.com. This vulnerability is uniquely identified as CVE-2016-5149 since 05/31/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. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/14/2022). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1059 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 93394 (openSUSE Security Update : Chromium (openSUSE-2016-2250)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236086 (Red Hat Update for chromium-browser (RHSA-2016:1854)).

Upgrading to version 53.0.2785.89 or 53.0.2785.92 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 (93394) and SecurityFocus (BID 92717†). See VDB-90558, VDB-90559, VDB-90560 and VDB-90561 for similar entries. 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.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: Code injection
CWE: CWE-94 / CWE-74 / CWE-707
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: 93394
Nessus Name: openSUSE Security Update : Chromium (openSUSE-2016-2250)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 865203
OpenVAS Name: Google Chrome Security Updates(stable-channel-update-for-desktop_31-2016-08)-MAC OS X
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 53.0.2785.89/53.0.2785.92

Timelineinfo

05/31/2016 🔍
08/31/2016 +92 days 🔍
08/31/2016 +0 days 🔍
08/31/2016 +0 days 🔍
09/04/2016 +4 days 🔍
09/09/2016 +5 days 🔍
09/11/2016 +2 days 🔍
09/14/2022 +2194 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update for Desktop, August 2016
Researcher: Nicolas Golubovic (OUSPG)
Organization: Zero Day Initiative
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-5149 (🔍)
GCVE (CVE): GCVE-0-2016-5149
GCVE (VulDB): GCVE-100-91053

OVAL: 🔍

SecurityFocus: 92717 - Google Chrome Prior to 53.0.2785.89 Multiple Security Vulnerabilities
SecurityTracker: 1036729

See also: 🔍

Entryinfo

Created: 09/04/2016 14:52
Updated: 09/14/2022 16:43
Changes: 09/04/2016 14:52 (72), 04/07/2019 20:33 (15), 09/14/2022 16:43 (5)
Complete: 🔍
Cache ID: 216:1AB: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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!