First published: Thu Nov 19 2020(Updated: )
Insufficient policy enforcement in File System API in Google Chrome on Windows prior to 89.0.4389.72 allowed a remote attacker to bypass filesystem restrictions via a crafted HTML page.
Credit: chrome-cve-admin@google.com Maciej Pulikowski
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 | |
Microsoft Windows | ||
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-21172 is classified as a high severity vulnerability due to its potential for exploitation by remote attackers to bypass filesystem restrictions.
To mitigate CVE-2021-21172, users should update Google Chrome to version 89.0.4389.72 or later.
CVE-2021-21172 affects Google Chrome versions prior to 89.0.4389.72 and allows remote attackers to bypass filesystem restrictions.
CVE-2021-21172 primarily impacts Google Chrome running on Windows and other operating systems that support the affected versions.
Yes, CVE-2021-21172 can be exploited through a crafted HTML page, which may allow for remote execution without direct user interaction.