CVE-2021-38019: Insufficient policy enforcement in CORS
Published Sep 20, 2021
·Updated
Insufficient policy enforcement in CORS in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Credit
Maurice Dauer
Affected Software
6 affected componentsFixes available
debian/chromium<=90.0.4430.212-1~deb10u1
116.0.5845.180-1~deb11u1118.0.5993.70-1~deb11u1116.0.5845.180-1~deb12u1118.0.5993.70-1~deb12u1118.0.5993.70-1
Google Chrome<96.0.4664.45
96.0.4664.45
Google Chrome<96.0.4664.45
Fedoraproject Fedora=34
Debian Debian Linux=10.0
Debian Debian Linux=11.0
Event History
Sep 20, 2021
CVE Published
12:00 AM
Dec 23, 2021
CVE Published
via MITRE·12:05 AM
Data Sourced
via MITRE·12:05 AM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
1
What is the severity of CVE-2021-38019?
CVE-2021-38019 is rated as a high severity vulnerability due to its potential for remote data leaks.
2
How do I fix CVE-2021-38019?
To fix CVE-2021-38019, users should update Google Chrome to version 96.0.4664.45 or later.
3
Which versions of Chrome are affected by CVE-2021-38019?
CVE-2021-38019 affects all versions of Google Chrome prior to 96.0.4664.45.
4
Can CVE-2021-38019 be exploited remotely?
Yes, CVE-2021-38019 can be exploited remotely by an attacker to leak cross-origin data.
5
What type of vulnerability is CVE-2021-38019?
CVE-2021-38019 is classified as a Cross-Origin Resource Sharing (CORS) vulnerability.