CVE-2017-5027: Bypass of Content Security Policy in BlinkCredit to 李普君 of 无声信息技术PKAV Team

Reference Links

• https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html (Advisory)
• https://crbug.com/661126

Parent vulnerabilities

(Appears in the following advisories)

• 5931754691533737707

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2017-5007
• CVE-2017-5006
• CVE-2017-5008
• CVE-2017-5010
• CVE-2017-5011
• CVE-2017-5009
• CVE-2017-5012
• CVE-2017-5028
• CVE-2017-5013
• CVE-2017-5014
• CVE-2017-5015
• CVE-2017-5019
• CVE-2017-5016
• CVE-2017-5017
• CVE-2017-5018
• CVE-2017-5020
• CVE-2017-5021
• CVE-2017-5022
• CVE-2017-5023
• CVE-2017-5024
• CVE-2017-5025
• CVE-2017-5026

Frequently Asked Questions

• What is the severity of CVE-2017-5027?

  CVE-2017-5027 has a high severity rating due to its potential for allowing remote attackers to bypass content security policy.

• How do I fix CVE-2017-5027?

  To fix CVE-2017-5027, it is recommended to update Google Chrome to version 56.0.2924.76 or later.

• What versions of Google Chrome are affected by CVE-2017-5027?

  CVE-2017-5027 affects Google Chrome versions prior to 56.0.2924.76 for desktop and versions before 56.0.2924.87 for Android.

• What type of attack is facilitated by CVE-2017-5027?

  CVE-2017-5027 facilitates remote attacks that allow attackers to execute scripts by bypassing the content security policy.

• Is CVE-2017-5027 a cross-site scripting vulnerability?

  Yes, CVE-2017-5027 is related to the improper enforcement of content security policy which can lead to cross-site scripting attacks.