Out-of-bounds memory access via stack overflow
Published Feb 22, 2021 · Updated Aug 3, 2024
Stack buffer overflow in Google Chrome Data Transfer before 88.0.4324.182 on Linux allows remote attackers to access memory via crafted HTML. The public Chrome record identifies the Data Transfer component but does not disclose the affected function or operation that overruns its stack buffer. The attack requires a user to open the page; Google has not published whether the out-of-bounds access yields code execution, data access, or only a crash.
Summary
What happened
Stack buffer overflow in Google Chrome Data Transfer before 88.0.4324.182 on Linux allows remote attackers to access memory via crafted HTML. The public Chrome record identifies the Data Transfer component but does not disclose the affected function or operation that overruns its stack buffer. The attack requires a user to open the page; Google has not published whether the out-of-bounds access yields code execution, data access, or only a crash.
The record
- CVE
- CVE-2021-21149
- Published
- Feb 22, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 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.182
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