Heap corruption via SwiftShader use-after-free
Published Mar 7, 2023 · Updated Oct 17, 2024
Use-after-free in SwiftShader in Google Chrome before 111.0.5563.64 allows remote attackers to corrupt heap memory via a crafted HTML page. Public details identify stale heap-object access in the SwiftShader rendering component, but Google has not disclosed the responsible function or lifetime error. Successful exploitation requires a user to open attacker-controlled HTML and results in heap corruption within the browser process.
Summary
What happened
Use-after-free in SwiftShader in Google Chrome before 111.0.5563.64 allows remote attackers to corrupt heap memory via a crafted HTML page. Public details identify stale heap-object access in the SwiftShader rendering component, but Google has not disclosed the responsible function or lifetime error. Successful exploitation requires a user to open attacker-controlled HTML and results in heap corruption within the browser process.
The record
- CVE
- CVE-2023-1213
- Published
- Mar 7, 2023
- Updated
- Oct 17, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 7, 2023CVE publishedPublication date reported by the CVE source.
- Oct 17, 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 <111.0.5563.64
- Affected versionversion=111.0.5563.64 <111.0.5563.64
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