Heap corruption via crafted Gamepad API input
Published Apr 4, 2022 · Updated Aug 2, 2024
Inappropriate Gamepad API handling in Google Chrome before 98.0.4758.102 allows remote attackers to trigger heap corruption via a crafted page. Google identifies the affected locus as the Gamepad API but has not disclosed the implementation error or the untrusted value that reaches the unsafe memory operation. Exploitation requires a user to open the crafted HTML page; the public record does not establish code execution or effects beyond heap corruption.
Summary
What happened
Inappropriate Gamepad API handling in Google Chrome before 98.0.4758.102 allows remote attackers to trigger heap corruption via a crafted page. Google identifies the affected locus as the Gamepad API but has not disclosed the implementation error or the untrusted value that reaches the unsafe memory operation. Exploitation requires a user to open the crafted HTML page; the public record does not establish code execution or effects beyond heap corruption.
The record
- CVE
- CVE-2022-0610
- Published
- Apr 4, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 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 <98.0.4758.102
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