Memory corruption via SwiftShader out-of-bounds write
Published Jul 16, 2024 · Updated Mar 17, 2025
Out-of-bounds write in SwiftShader in Google Chrome before 117.0.5938.62 allows remote attackers to corrupt memory via a crafted HTML page. Google identifies the faulty component as SwiftShader but has not published the specific function, buffer, or bounds-check failure that writes beyond the intended memory region. Exploitation requires a user to load attacker-controlled HTML, and the published record establishes memory corruption rather than a specific follow-on outcome.
Summary
What happened
Out-of-bounds write in SwiftShader in Google Chrome before 117.0.5938.62 allows remote attackers to corrupt memory via a crafted HTML page. Google identifies the faulty component as SwiftShader but has not published the specific function, buffer, or bounds-check failure that writes beyond the intended memory region. Exploitation requires a user to load attacker-controlled HTML, and the published record establishes memory corruption rather than a specific follow-on outcome.
The record
- CVE
- CVE-2024-3176
- Published
- Jul 16, 2024
- Updated
- Mar 17, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2024CVE publishedPublication date reported by the CVE source.
- Mar 17, 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 <117.0.5938.62
- Affected versionversion=117.0.5938.62 <117.0.5938.62
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