Heap corruption via SwiftShader out-of-bounds write
Published May 30, 2023 · Updated May 5, 2025
Out-of-bounds write in Google Chrome before 114.0.5735.90 allows remote attackers to corrupt heap memory through crafted HTML. The public advisory identifies SwiftShader as the affected component but does not disclose the faulty function or missing bounds operation. A user must open the crafted page; exploitation produces heap corruption with confidentiality, integrity, and availability impact.
Summary
What happened
Out-of-bounds write in Google Chrome before 114.0.5735.90 allows remote attackers to corrupt heap memory through crafted HTML. The public advisory identifies SwiftShader as the affected component but does not disclose the faulty function or missing bounds operation. A user must open the crafted page; exploitation produces heap corruption with confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2023-2929
- Published
- May 30, 2023
- Updated
- May 5, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 30, 2023CVE publishedPublication date reported by the CVE source.
- May 5, 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=114.0.5735.90 <114.0.5735.90
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