What is the severity of CVE-2017-5022?

CVE-2017-5022 is considered a high-severity vulnerability due to its potential for exploitation through unsafe-inline content security policies.

How do I fix CVE-2017-5022?

To fix CVE-2017-5022, upgrade to Google Chrome version 56.0.2924.76 or later for Linux, Windows, and Mac, or 56.0.2924.87 for Android.

What type of systems are affected by CVE-2017-5022?

CVE-2017-5022 affects Google Chrome versions prior to 56.0.2924.76 on Linux, Windows, Mac, and versions prior to 56.0.2924.87 on Android.

What can an attacker achieve with CVE-2017-5022?

An attacker can bypass the content security policy and execute malicious scripts by using a crafted HTML page.

Is there a workaround for CVE-2017-5022?

There are no effective workarounds for CVE-2017-5022 other than applying the necessary software updates.

Vulnerability/
CVE-2017-5022

medium

4.3

17/2/2017

5/8/2024

CVE-2017-5022

First published: Fri Feb 17 2017(Updated: )

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.

Credit: cve-coordination@google.com

Affected Software	Affected Version	How to fix
Google Chrome	<=55.0.2883.87

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-5022?
CVE-2017-5022 is considered a high-severity vulnerability due to its potential for exploitation through unsafe-inline content security policies.
How do I fix CVE-2017-5022?
To fix CVE-2017-5022, upgrade to Google Chrome version 56.0.2924.76 or later for Linux, Windows, and Mac, or 56.0.2924.87 for Android.
What type of systems are affected by CVE-2017-5022?
CVE-2017-5022 affects Google Chrome versions prior to 56.0.2924.76 on Linux, Windows, Mac, and versions prior to 56.0.2924.87 on Android.
What can an attacker achieve with CVE-2017-5022?
An attacker can bypass the content security policy and execute malicious scripts by using a crafted HTML page.
Is there a workaround for CVE-2017-5022?
There are no effective workarounds for CVE-2017-5022 other than applying the necessary software updates.

agent/type
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
agent/severity
agent/references
agent/author
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/trending
agent/tags
agent/source
vendor/google
canonical/google chrome
version/google chrome/55.0.2883.87

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-5022?
CVE-2017-5022 is considered a high-severity vulnerability due to its potential for exploitation through unsafe-inline content security policies.
How do I fix CVE-2017-5022?
To fix CVE-2017-5022, upgrade to Google Chrome version 56.0.2924.76 or later for Linux, Windows, and Mac, or 56.0.2924.87 for Android.
What type of systems are affected by CVE-2017-5022?
CVE-2017-5022 affects Google Chrome versions prior to 56.0.2924.76 on Linux, Windows, Mac, and versions prior to 56.0.2924.87 on Android.
What can an attacker achieve with CVE-2017-5022?
An attacker can bypass the content security policy and execute malicious scripts by using a crafted HTML page.
Is there a workaround for CVE-2017-5022?
There are no effective workarounds for CVE-2017-5022 other than applying the necessary software updates.