Google Chrome up to 56 Content Security Policy 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.
7.0$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Google Chrome up to 56. Affected by this vulnerability is an unknown functionality of the component Content Security Policy. This manipulation causes cross site scripting. This vulnerability is registered as CVE-2017-5018. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Google Chrome up to 56 (Web Browser). Affected by this vulnerability is some unknown processing of the component Content Security Policy. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, had an insufficiently strict content security policy on the Chrome app launcher page, which allowed a remote attacker to inject scripts or HTML into a privileged page via a crafted HTML page.

The bug was discovered 01/25/2017. The weakness was published 02/17/2017 by Armin Razmdjou (Paul) with Tresorit (Website). It is possible to read the advisory at chromereleases.googleblog.com. This vulnerability is known as CVE-2017-5018 since 01/02/2017. 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 T1059.007 according to MITRE ATT&CK.

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), SecurityFocus (BID 95792†) and SecurityTracker (ID 1037718†). Similar entries are available at VDB-96042, VDB-96043, VDB-96044 and VDB-96045. 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: 7.2
VulDB Meta Temp Score: 7.0

VulDB Base Score: 8.3
VulDB Temp Score: 7.9
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: 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 🔍
02/16/2025 +2921 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

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

CVE: CVE-2017-5018 (🔍)
GCVE (CVE): GCVE-0-2017-5018
GCVE (VulDB): GCVE-100-97075

OVAL: 🔍

SecurityFocus: 95792 - Google Chrome Multiple Security Vulnerabilities
OSVDB: - CVE-2017-5018 - Google - Chrome - Cross-Site Scripting Issue
SecurityTracker: 1037718

See also: 🔍

Entryinfo

Created: 02/17/2017 16:11
Updated: 02/16/2025 02:53
Changes: 02/17/2017 16:11 (80), 08/15/2020 16:19 (6), 02/16/2025 02:53 (19)
Complete: 🔍
Cache ID: 216:EC4: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 ▸

Interested in the pricing of exploits?

See the underground prices here!