Heap corruption via unvalidated shared-memory fragment bounds
Published Aug 1, 2023 · Updated Feb 13, 2025
Out-of-bounds memory access in Google Chrome before 115.0.5790.98 allows remote attackers to corrupt heap memory via crafted HTML. Mojo's ipcz code mapped untrusted FragmentDescriptor offsets and sizes into shared memory without first verifying that the described span stayed within the mapped buffer. Exploitation requires control of a renderer process and user interaction with the crafted page; the public record bounds the result to heap corruption.
Summary
What happened
Out-of-bounds memory access in Google Chrome before 115.0.5790.98 allows remote attackers to corrupt heap memory via crafted HTML. Mojo's ipcz code mapped untrusted FragmentDescriptor offsets and sizes into shared memory without first verifying that the described span stayed within the mapped buffer. Exploitation requires control of a renderer process and user interaction with the crafted page; the public record bounds the result to heap corruption.
The record
- CVE
- CVE-2023-3732
- Published
- Aug 1, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 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=115.0.5790.98 <115.0.5790.98
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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