Heap corruption via Browser History buffer overflow
Published Apr 4, 2023 · Updated Feb 13, 2025
Heap buffer overflow in Google Chrome Browser History before 112.0.5615.49 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the Browser History component, but the restricted issue record leaves the faulty allocation or write operation undisclosed. Exploitation requires a user to open a crafted page and perform specific UI interaction; the published record establishes heap corruption but no more specific outcome.
Summary
What happened
Heap buffer overflow in Google Chrome Browser History before 112.0.5615.49 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the Browser History component, but the restricted issue record leaves the faulty allocation or write operation undisclosed. Exploitation requires a user to open a crafted page and perform specific UI interaction; the published record establishes heap corruption but no more specific outcome.
The record
- CVE
- CVE-2023-1820
- Published
- Apr 4, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=0 <112.0.5615.49
- Affected versionversion=112.0.5615.49 <112.0.5615.49
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