First published: Mon Apr 24 2017(Updated: )
Blink in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android failed to correctly propagate CSP restrictions to local scheme pages, which allowed a remote attacker to bypass content security policy via a crafted HTML page, related to the unsafe-inline keyword.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
Google Chrome | <=57.0.2987.75 | |
macOS | ||
Linux Kernel | ||
Microsoft Windows Operating System | ||
Google Chrome | <=57.0.2987.100 | |
Android | ||
Debian Linux | =8.0 | |
Debian Linux | =9.0 | |
Red Hat Enterprise Linux Desktop | =6.0 | |
Red Hat Enterprise Linux Server | =6.0 | |
Red Hat Enterprise Linux Workstation | =6.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-5033 is rated as high severity due to its ability to bypass content security policies.
To fix CVE-2017-5033, update Google Chrome to version 57.0.2987.98 or later.
CVE-2017-5033 affects Google Chrome versions prior to 57.0.2987.98.
CVE-2017-5033 affects Google Chrome on Mac, Windows, Linux, and Android platforms.
Yes, CVE-2017-5033 allows for the bypassing of content security policy on local scheme pages.