Use after free in Blink in Google Chrome prior to 89.0.4389.128 allowed a remote attacker to potentially exploit heap corruption via a craft
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 89.0.4389.128
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Google Chrome, the web browser, is affected by this vulnerability in its Blink rendering engine. A remote attacker could potentially exploit it by tricking a user into opening a specially crafted web page, which could corrupt memory and may allow malicious code to run.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Use after free in Blink in Google Chrome prior to 89.0.4389.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
Affected versions
- Google Chrome
From unspecified · fixed in 89.0.4389.128
References 6
crbug.com
chromereleases.googleblog.com
security.gentoo.org
lists.fedoraproject.org
Questions about CVE-2021-21206
What does this mean?
Blink, the rendering engine used by Chromium and Google Chrome, uses memory after it has been freed. This can corrupt the heap, the memory area programs use for dynamic data.Source: security.gentoo.org, lists.fedoraproject.org
Am I affected, and how do I check?
The CVE description lists Google Chrome before 89.0.4389.128, while the conditions list Chromium and Chrome builds before 90.0.4430.93. To check a installed build, open chrome://version or Help > About and compare the version number with these values.Source: security.gentoo.org, lists.fedoraproject.org
What should I do about it?
Update to Chromium 90.0.4430.93, as the fix quote directs. Check the version against the listed fixed builds after updating.Source: security.gentoo.org, lists.fedoraproject.org
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data