Heap corruption via Bookmarks buffer overflow
Published Feb 11, 2022 · Updated Aug 2, 2024
Heap buffer overflow in Google Chrome Bookmarks before 97.0.4692.71 allows remote attackers to corrupt heap memory after a user gesture. Google identifies the Bookmarks component but has not published the affected function or the malformed-data operation that writes beyond the heap buffer. Exploitation requires convincing a user to perform a specific gesture; the published consequence is heap corruption in the browser process.
Summary
What happened
Heap buffer overflow in Google Chrome Bookmarks before 97.0.4692.71 allows remote attackers to corrupt heap memory after a user gesture. Google identifies the Bookmarks component but has not published the affected function or the malformed-data operation that writes beyond the heap buffer. Exploitation requires convincing a user to perform a specific gesture; the published consequence is heap corruption in the browser process.
The record
- CVE
- CVE-2022-0101
- Published
- Feb 11, 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 11, 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.71
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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