CVE-2017-5027
"Google Chrome Blink CVE - Content Security Policy Bypass"
Description
Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to properly enforce unsafe-inline content security policy, which allowed a remote attacker to bypass content security policy via a crafted HTML page.
INFO
Published Date :
Feb. 17, 2017, 7:59 a.m.
Last Modified :
Nov. 21, 2024, 3:26 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
1.4
Exploitability Score :
2.8
Public PoC/Exploit Available at Github
CVE-2017-5027 has a 1 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2017-5027.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Monitoring plugin to check for open CVE numbers against your local Debian packages
Shell
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2017-5027 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2017-5027 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Source Update by [email protected]
Nov. 07, 2023
Action Type Old Value New Value Changed Source Google Inc. Chrome -
CVE Modified by [email protected]
Nov. 07, 2023
Action Type Old Value New Value Added Reference Chrome https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html [No types assigned] Added Reference Chrome https://crbug.com/661126 [No types assigned] Removed Reference Google Inc. https://crbug.com/661126 Removed Reference Google Inc. https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html -
CWE Remap by [email protected]
Oct. 03, 2019
Action Type Old Value New Value Changed CWE CWE-284 NVD-CWE-noinfo -
Initial Analysis by [email protected]
Feb. 17, 2017
Action Type Old Value New Value Added CVSS V2 (AV:N/AC:M/Au:N/C:N/I:P/A:N) Added CVSS V3 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N Changed Reference Type https://crbug.com/661126 No Types Assigned https://crbug.com/661126 Permissions Required Changed Reference Type https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html No Types Assigned https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html Vendor Advisory Added CWE CWE-284 Added CPE Configuration OR *cpe:2.3:a:google:chrome:55.0.2883.87:*:*:*:*:*:*:* (and previous)
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2017-5027 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2017-5027
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.17 }} 0.05%
score
0.54634
percentile