Heap corruption via SwiftShader use-after-free
Published Jun 24, 2024 · Updated Feb 13, 2025
Use-after-free in Google Chrome's SwiftShader before 126.0.6478.126 allows remote attackers to corrupt heap memory through crafted HTML. SwiftShader accesses an object after its lifetime ends; public issue details do not identify the object, function, or exact operation. Exploitation requires a user to visit the crafted page and can compromise the browser process's confidentiality, integrity, and availability.
Summary
What happened
Use-after-free in Google Chrome's SwiftShader before 126.0.6478.126 allows remote attackers to corrupt heap memory through crafted HTML. SwiftShader accesses an object after its lifetime ends; public issue details do not identify the object, function, or exact operation. Exploitation requires a user to visit the crafted page and can compromise the browser process's confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-6291
- Published
- Jun 24, 2024
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2024CVE 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 <126.0.6478.126
- Affected versionversion=126.0.6478.126 <126.0.6478.126
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