CVE-2021-38019: Insufficient policy enforcement in CORS
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
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 96.0.4664.45 - Upgrade
Upgrade
alpine/qt5-qtwebengineto a version that resolves this vulnerability.Fixed in 5.15.3_git20211112-r1 - Upgrade
Upgrade
alpine/qt5-qtwebengineto a version that resolves this vulnerability.Fixed in 5.15.3_git20211127-r1 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 150.0.7871.100-1~deb12u1Fixed in 156.0.8078.79-1~deb12u1Fixed in 150.0.7871.181-1~deb13u1Fixed in 156.0.8078.79-1~deb13u1Fixed in 156.0.8078.79-1
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
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.
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.
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.
Can CVE-2021-38019 be exploited remotely?
Yes, CVE-2021-38019 can be exploited remotely by an attacker to leak cross-origin data.
What type of vulnerability is CVE-2021-38019?
CVE-2021-38019 is classified as a Cross-Origin Resource Sharing (CORS) vulnerability.