Heap corruption via Data Transfer use-after-free
Published Feb 12, 2022 · Updated Aug 2, 2024
A Data Transfer use-after-free in Google Chrome before 97.0.4692.99 on Chrome OS lets remote attackers corrupt heap memory via crafted HTML. Google identifies the affected locus only as Data Transfer and has not published which object is freed and later dereferenced. Exploitation requires specific user interaction with the crafted page; consequences beyond heap corruption remain undisclosed.
Summary
What happened
A Data Transfer use-after-free in Google Chrome before 97.0.4692.99 on Chrome OS lets remote attackers corrupt heap memory via crafted HTML. Google identifies the affected locus only as Data Transfer and has not published which object is freed and later dereferenced. Exploitation requires specific user interaction with the crafted page; consequences beyond heap corruption remain undisclosed.
The record
- CVE
- CVE-2022-0308
- Published
- Feb 12, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, 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