Heap corruption via mutable Mojo IPC messages
Published May 30, 2023 · Updated May 5, 2025
Out-of-bounds memory access in Google Chrome before 114.0.5735.90 allows remote attackers to corrupt the heap via crafted HTML. During Mojo IPC deserialization, core_ipcz exposes message contents in shared memory even though validators assume that the bytes cannot change. A user must open the crafted page; concurrent message mutation can bypass validation and cause out-of-bounds access that corrupts the browser heap.
Summary
What happened
Out-of-bounds memory access in Google Chrome before 114.0.5735.90 allows remote attackers to corrupt the heap via crafted HTML. During Mojo IPC deserialization, core_ipcz exposes message contents in shared memory even though validators assume that the bytes cannot change. A user must open the crafted page; concurrent message mutation can bypass validation and cause out-of-bounds access that corrupts the browser heap.
The record
- CVE
- CVE-2023-2934
- Published
- May 30, 2023
- Updated
- May 5, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1189
- 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
- Chrome Mojo Message Validation Bypassproof of concept · demonstrated
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