CVE-2017-5033

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.

Exploit odds

1.7% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2017-04-24 23:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:19 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.7% in the next 30 days (EPSS).
• Severity: 4.3 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2017-04-24 23:59 UTC

Last modified

2026-06-17 01:19 UTC

Exploit probability

1.7% · EPSS, next 30 days

Weakness

CWE-281

Record status

Modified

Affected

• Google Chrome ≤ 57.0.2987.75
• Google Chrome ≤ 57.0.2987.100
• Debian Linux 8.0
• Debian Linux 9.0
• Redhat Enterprise Linux Desktop 6.0
• Redhat Enterprise Linux Server 6.0
• Redhat Enterprise Linux Workstation 6.0

Attack profile CVSS 3.1 · 4.3

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-5033.md and follow it. Check whether this project is affected by CVE-2017-5033. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge