Heap corruption via History buffer overflow
Published Jun 4, 2021 · Updated Aug 3, 2024
Heap buffer overflow in Google Chrome History before 90.0.4430.212 allows remote attackers to corrupt heap memory through crafted HTML. Google identifies the History component and bug class, but the restricted issue report leaves the faulty function, bounds check, and memory operation undisclosed. The attacker must first compromise the renderer process, making this a post-renderer-compromise memory-corruption path rather than a standalone initial-access flaw.
Summary
What happened
Heap buffer overflow in Google Chrome History before 90.0.4430.212 allows remote attackers to corrupt heap memory through crafted HTML. Google identifies the History component and bug class, but the restricted issue report leaves the faulty function, bounds check, and memory operation undisclosed. The attacker must first compromise the renderer process, making this a post-renderer-compromise memory-corruption path rather than a standalone initial-access flaw.
The record
- CVE
- CVE-2021-30516
- Published
- Jun 4, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <90.0.4430.212
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo