Google Chrome up to 55 Blink cross site scripting

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

Summaryinfo

A vulnerability was found in Google Chrome up to 55 and classified as critical. This issue affects some unknown processing of the component Blink. The manipulation results in cross site scripting. This vulnerability is cataloged as CVE-2016-5207. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Google Chrome up to 55 (Web Browser). Affected is an unknown code of the component Blink. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

In Blink in Google Chrome prior to 55.0.2883.75 for Mac, Windows and Linux, and 55.0.2883.84 for Android, corruption of the DOM tree could occur during the removal of a full screen element, which allowed a remote attacker to achieve arbitrary code execution via a crafted HTML page.

The bug was discovered 12/01/2016. The weakness was shared 01/19/2017 by Abdulrahman Alqabandi (xisigr) with Qihoo 360 (Website). The advisory is shared for download at securityfocus.com. This vulnerability is traded as CVE-2016-5207 since 05/31/2016. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.007.

The vulnerability was handled as a non-public zero-day exploit for at least 8 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 95661 (Ubuntu 14.04 LTS / 16.04 LTS / 16.10 : oxide-qt vulnerabilities (USN-3153-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Ubuntu Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236207 (Red Hat Update for Chromium-browser Security (RHSA-2016:2919)).

Upgrading to version 55.0.2883.75 eliminates this vulnerability. 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 (95661) and SecurityFocus (BID 94633†). The entries VDB-95480, VDB-95481, VDB-95482 and VDB-95483 are related to this item. Once again VulDB remains the best source 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: 6.7
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.1
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Cross site scripting
CWE: CWE-79 / CWE-94 / CWE-74
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: 95661
Nessus Name: Ubuntu 14.04 LTS / 16.04 LTS / 16.10 : oxide-qt vulnerabilities (USN-3153-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 900236
OpenVAS Name: SuSE Update for Chromium openSUSE-SU-2016:3108-1 (Chromium)
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 55.0.2883.75

Timelineinfo

05/31/2016 🔍
12/01/2016 +184 days 🔍
12/01/2016 +0 days 🔍
12/09/2016 +8 days 🔍
12/09/2016 +0 days 🔍
01/19/2017 +41 days 🔍
01/19/2017 +0 days 🔍
01/19/2017 +0 days 🔍
05/14/2026 +3401 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: USN-3153-1⛔
Researcher: Abdulrahman Alqabandi (xisigr)
Organization: Qihoo 360
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-5207 (🔍)
GCVE (CVE): GCVE-0-2016-5207
GCVE (VulDB): GCVE-100-95484

OVAL: 🔍

SecurityFocus: 94633 - Google Chrome Prior to 55.0.2883.75 Multiple Security Vulnerabilities
OSVDB: - CVE-2016-5207 - Google - Chrome - Code Execution Issue

See also: 🔍

Entryinfo

Created: 01/19/2017 09:41
Updated: 05/14/2026 01:32
Changes: 01/19/2017 09:41 (76), 07/24/2020 14:49 (10), 11/01/2022 11:01 (4), 11/01/2022 11:07 (1), 05/14/2026 01:32 (17)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!