Heap corruption via Service Worker out-of-bounds write
Published Apr 19, 2023 · Updated Feb 13, 2025
Out-of-bounds write in Google Chrome before 112.0.5615.137 allows remote attackers to corrupt heap memory via a crafted HTML page. The Service Worker API writes outside an allocated buffer, but Google has not disclosed the responsible function or unchecked operation. Opening the crafted page is required; successful exploitation can crash or subvert the browser process.
Summary
What happened
Out-of-bounds write in Google Chrome before 112.0.5615.137 allows remote attackers to corrupt heap memory via a crafted HTML page. The Service Worker API writes outside an allocated buffer, but Google has not disclosed the responsible function or unchecked operation. Opening the crafted page is required; successful exploitation can crash or subvert the browser process.
The record
- CVE
- CVE-2023-2133
- Published
- Apr 19, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 19, 2023CVE 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 <112.0.5615.137
- Affected versionversion=112.0.5615.137 <112.0.5615.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