Heap corruption via crafted malicious extension
Published Feb 9, 2021 · Updated Aug 3, 2024
Heap buffer overflow in Google Chrome before 88.0.4324.146 allows attackers to corrupt heap memory through a crafted malicious extension. The public bug report is access-restricted, and Google has not disclosed which extension-processing operation writes beyond the heap buffer. A victim must install the extension before the faulty path is reached; the public record identifies exploitable heap corruption as the bounded consequence.
Summary
What happened
Heap buffer overflow in Google Chrome before 88.0.4324.146 allows attackers to corrupt heap memory through a crafted malicious extension. The public bug report is access-restricted, and Google has not disclosed which extension-processing operation writes beyond the heap buffer. A victim must install the extension before the faulty path is reached; the public record identifies exploitable heap corruption as the bounded consequence.
The record
- CVE
- CVE-2021-21143
- Published
- Feb 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 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 <88.0.4324.146
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