CVE-2019-5811: CORS bypass in Blink
Published Oct 4, 2017
·Updated
Incorrect handling of CORS in ServiceWorker in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to bypass same origin policy via a crafted HTML page.
Credit
Jun Kokatsu@@shhnjk
Affected Software
10 affected componentsFixes available
debian/chromium
90.0.4430.212-1~deb10u1116.0.5845.180-1~deb11u1120.0.6099.129-1~deb11u1119.0.6045.199-1~deb12u1120.0.6099.129-1~deb12u1120.0.6099.129-1
Google Chrome<74.0.3729.108
74.0.3729.108
Google Chrome<74.0.3729.108
Debian Debian Linux=10.0
Fedoraproject Fedora=29
Fedoraproject Fedora=30
openSUSE Backports=sle-15
openSUSE Leap=15.0
openSUSE Leap=15.1
openSUSE Leap=42.3
Event History
Oct 4, 2017
CVE Published
12:00 AM
Jun 27, 2019
CVE Published
via MITRE·04:13 PM
Data Sourced
via MITRE·04:13 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
1
What is the severity of CVE-2019-5811?
CVE-2019-5811 has a high severity rating due to its potential to bypass the same origin policy.
2
How do I fix CVE-2019-5811?
To fix CVE-2019-5811, update Google Chrome to version 74.0.3729.108 or later.
3
Which versions of Google Chrome are affected by CVE-2019-5811?
Google Chrome versions prior to 74.0.3729.108 are affected by CVE-2019-5811.
4
What type of vulnerability is CVE-2019-5811?
CVE-2019-5811 is an incorrect handling of CORS vulnerability in ServiceWorker.
5
Can CVE-2019-5811 affect other software apart from Google Chrome?
Yes, CVE-2019-5811 can also affect Chromium running on various operating systems, including Debian and Fedora.