Heap corruption via Passwords use-after-free
Published Aug 21, 2024 · Updated Aug 27, 2024
Use-after-free in Google Chrome's Passwords component before 128.0.6613.84 allows remote attackers to corrupt heap memory via crafted HTML. Google has not disclosed which Passwords code path retains or dereferences the freed allocation. Successful exploitation requires a user to open attacker-controlled HTML and exposes browser data, execution integrity, and process availability.
Summary
What happened
Use-after-free in Google Chrome's Passwords component before 128.0.6613.84 allows remote attackers to corrupt heap memory via crafted HTML. Google has not disclosed which Passwords code path retains or dereferences the freed allocation. Successful exploitation requires a user to open attacker-controlled HTML and exposes browser data, execution integrity, and process availability.
The record
- CVE
- CVE-2024-7964
- Published
- Aug 21, 2024
- Updated
- Aug 27, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 27, 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=0 <128.0.6613.84
- Affected versionversion=128.0.6613.84 <128.0.6613.84
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