Heap corruption via Safe Browsing use-after-free
Published Aug 12, 2022 · Updated Aug 3, 2024
Use-after-free in Google Chrome Safe Browsing before 104.0.5112.79 allows remote attackers to corrupt heap memory via crafted HTML. The public advisory identifies Safe Browsing but does not disclose the affected class, function, or lifetime error that leaves a freed object accessible. The attack requires a user to open the page, and the public record establishes heap corruption but does not document a sandbox escape or final payload.
Summary
What happened
Use-after-free in Google Chrome Safe Browsing before 104.0.5112.79 allows remote attackers to corrupt heap memory via crafted HTML. The public advisory identifies Safe Browsing but does not disclose the affected class, function, or lifetime error that leaves a freed object accessible. The attack requires a user to open the page, and the public record establishes heap corruption but does not document a sandbox escape or final payload.
The record
- CVE
- CVE-2022-2604
- Published
- Aug 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <104.0.5112.79
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