CVE-2019-5822: CORS bypass in download manager
Published Jan 29, 2019
·Updated
Inappropriate implementation in Blink 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, Microsoft Browser Vulnerability Research
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
openSUSE Backports=sle-15
openSUSE Leap=15.0
openSUSE Leap=15.1
openSUSE Leap=42.3
Debian Debian Linux=10.0
Fedoraproject Fedora=29
Fedoraproject Fedora=30
Remediation
Event History
Jan 29, 2019
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 vulnerability ID of this issue?
The vulnerability ID is CVE-2019-5822.
2
What is the severity of CVE-2019-5822?
The severity of CVE-2019-5822 is high (8.8).
3
How does this vulnerability affect Google Chrome?
This vulnerability affects Google Chrome versions prior to 74.0.3729.108.
4
How can a remote attacker exploit this vulnerability?
A remote attacker can exploit this vulnerability by bypassing the same origin policy via a crafted HTML page.
5
Is there a fix available for CVE-2019-5822?
Yes, a fix is available. Users should update to Google Chrome version 74.0.3729.108 or higher.