Google Chrome up to 56 Blink Universal 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.
5.9$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Google Chrome up to 56. This impacts an unknown function of the component Blink. The manipulation leads to cross site scripting (Universal). This vulnerability is listed as CVE-2017-5008. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 56 (Web Browser). It has been rated as critical. This issue affects an unknown code of the component Blink. The manipulation with an unknown input leads to a cross site scripting vulnerability (Universal). Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, allowed attacker controlled JavaScript to be run during the invocation of a private script method, which allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) via a crafted HTML page.

The bug was discovered 01/25/2017. The weakness was presented 02/17/2017 by Armin Razmdjou (Paul) with Tresorit (Website). The advisory is shared at chromereleases.googleblog.com. The identification of this vulnerability is CVE-2017-5008 since 01/02/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. 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 T1059.007 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 96826 (RHEL 6 : chromium-browser (RHSA-2017:0206)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236251 (Red Hat Update forchromium-browser Security (RHSA-2017:0206)).

Upgrading eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (96826) and SecurityFocus (BID 95792†). See VDB-96042, VDB-96043, VDB-96044 and VDB-96045 for similar entries. 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.2
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.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

Name: Universal
Class: Cross site scripting / Universal
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: 96826
Nessus Name: RHEL 6 : chromium-browser (RHSA-2017:0206)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 703776
OpenVAS Name: Debian Security Advisory DSA 3776-1 (chromium-browser - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/02/2017 🔍
01/25/2017 +23 days 🔍
01/25/2017 +0 days 🔍
01/26/2017 +1 days 🔍
01/27/2017 +1 days 🔍
02/17/2017 +21 days 🔍
02/17/2017 +0 days 🔍
02/17/2017 +0 days 🔍
08/15/2020 +1275 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: chromereleases.googleblog.com
Researcher: Armin Razmdjou (Paul)
Organization: Tresorit
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-5008 (🔍)
GCVE (CVE): GCVE-0-2017-5008
GCVE (VulDB): GCVE-100-97073

OVAL: 🔍

SecurityFocus: 95792 - Google Chrome Multiple Security Vulnerabilities
OSVDB: - CVE-2017-5008 - Google - Chrome - Universal Cross-Site Scripting Issue

See also: 🔍

Entryinfo

Created: 02/17/2017 16:10
Updated: 08/15/2020 16:14
Changes: 02/17/2017 16:10 (81), 08/15/2020 16:14 (6)
Complete: 🔍
Cache ID: 216:255: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 ▸

Want to know what is going to be exploited?

We predict KEV entries!