CVE-2021-21166
Google Chromium Race Condition
- Published9 Mar 2021
- Added to CISA KEV3 Nov 2021
- Remediation due17 Nov 2021
Description
Data race in audio in Google Chrome prior to 89.0.4389.72 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://chromereleases.googleblog.com/2021/03/stable-channel-update-for-desktop.html
- https://crbug.com/1177465
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BBT54RKAE5XLMWSHLVUKJ7T2XHHYMXLH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FE5SIKEVYTMDCC5OSXGOM2KRPYLHYMQX/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LCIDZ77XUDMB2EBPPWCQXPEIJERDNSNT/
- https://security.gentoo.org/glsa/202104-08
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-21166
- https://www.debian.org/security/2021/dsa-4886
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2021-21166 being actively exploited?
Yes. CVE-2021-21166 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 3 Nov 2021.
How severe is CVE-2021-21166?
CVE-2021-21166 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 24.0% probability of exploitation.
Which products are affected by CVE-2021-21166?
Affected products include Google Chrome, Debian Linux, Fedoraproject Fedora.
How do I fix CVE-2021-21166?
Upgrade affected software to a fixed version, for example Google Chrome 89.0.4389.72 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2021-21166 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.