Heap corruption via Autofill use-after-free
Published Sep 11, 2024 · Updated Sep 13, 2024
Use-after-free in Google Chrome Autofill before 128.0.6613.137 allows remote attackers to corrupt heap memory with crafted HTML. The public record identifies Autofill but does not disclose the freed object, lifetime error, or responsible function because the Chromium issue is access-restricted. Exploitation requires user interaction with an attacker-controlled page; the published record bounds the result to browser heap corruption.
Summary
What happened
Use-after-free in Google Chrome Autofill before 128.0.6613.137 allows remote attackers to corrupt heap memory with crafted HTML. The public record identifies Autofill but does not disclose the freed object, lifetime error, or responsible function because the Chromium issue is access-restricted. Exploitation requires user interaction with an attacker-controlled page; the published record bounds the result to browser heap corruption.
The record
- CVE
- CVE-2024-8639
- Published
- Sep 11, 2024
- Updated
- Sep 13, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 11, 2024CVE publishedPublication date reported by the CVE source.
- Sep 13, 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.137
- Affected versionversion=128.0.6613.137 <128.0.6613.137
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