Use after free in Indexed DB API in Google Chrome prior to 93.0.4577.82 allowed a remote attacker who had compromised the renderer process t
- 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 93.0.4577.82
- 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's Indexed DB API contains a memory-handling flaw that could let an attacker who had already taken control of the browser's renderer process escape the browser sandbox. Exploitation would require a crafted web page.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Use after free in Indexed DB API in Google Chrome prior to 93.0.4577.82 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Google Chrome
From unspecified · fixed in 93.0.4577.82
References 4
chromereleases.googleblog.com
crbug.com
Questions about CVE-2021-30633
What does this mean?
This is a use-after-free bug in Chrome's Indexed DB API, meaning the browser can use memory after it has been released. The advisory says it allowed a remote attacker who had already compromised the renderer process to take advantage of it.Source: lists.fedoraproject.org
Am I affected, and how do I check?
The listed range is Google Chrome prior to 93.0.4577.82, and a separate source names the chromium-browser package. To check a Chrome install, open the browser's About page or run its version command and compare the number against that range.Source: lists.fedoraproject.org
What should I do about it?
The fix quote says to update to 94.0.4606.61. Installing that version or a later Chrome release is the stated remedy.Source: 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