Heap corruption via Task Manager overflow
Published Feb 12, 2022 · Updated Aug 2, 2024
Heap buffer overflow in Task Manager in Google Chrome before 97.0.4692.99 allows remote attackers to trigger heap corruption via specific user interactions. The overflow occurs while Task Manager processes interaction data, but Google has not published the exact faulty operation or code locus. An attacker must induce a user to perform the specified interaction; resulting corruption can interrupt the browser and may enable code execution, while the advisory confirms no more specific outcome.
Summary
What happened
Heap buffer overflow in Task Manager in Google Chrome before 97.0.4692.99 allows remote attackers to trigger heap corruption via specific user interactions. The overflow occurs while Task Manager processes interaction data, but Google has not published the exact faulty operation or code locus. An attacker must induce a user to perform the specified interaction; resulting corruption can interrupt the browser and may enable code execution, while the advisory confirms no more specific outcome.
The record
- CVE
- CVE-2022-0310
- Published
- Feb 12, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 <97.0.4692.99
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