First published: Wed Feb 05 2020(Updated: )
Insufficient policy enforcement in navigations in Google Chrome prior to 89.0.4389.72 allowed a remote attacker who had compromised the renderer process to bypass navigation restrictions via a crafted HTML page.
Credit: chrome-cve-admin@google.com Luan Herrera @lbherrera_
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | 90.0.4430.212-1~deb10u1 116.0.5845.180-1~deb11u1 118.0.5993.70-1~deb11u1 116.0.5845.180-1~deb12u1 118.0.5993.70-1~deb12u1 118.0.5993.70-1 | |
Google Chrome (Trace Event) | <89.0.4389.72 | 89.0.4389.72 |
Google Chrome (Trace Event) | <89.0.4389.72 | |
Fedora | =32 | |
Fedora | =33 | |
Fedora | =34 | |
Debian | =10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2021-21182 is classified as a high severity vulnerability due to the potential for remote code execution.
To fix CVE-2021-21182, update Google Chrome to version 90.0.4430.212 or later.
CVE-2021-21182 affects Google Chrome versions prior to 89.0.4389.72.
Yes, CVE-2021-21182 can be exploited remotely if the attacker has access to a compromised renderer process.
CVE-2021-21182 specifically affects Google Chrome and Chromium-based browsers prior to the specified patched versions.