Out-of-bounds write via invalid Mojo quantity
Published Nov 27, 2024 · Updated Nov 20, 2025
Out-of-bounds write in Mojo in Google Chrome before 129.0.6668.89 allows remote attackers to corrupt memory via crafted HTML. Mojo insufficiently validates a supplied quantity before a memory write, allowing the operation to exceed its intended bounds; Google has not disclosed the affected function or field. Exploitation requires prior renderer-process compromise, and the published record demonstrates memory corruption rather than a separate code-execution result.
Summary
What happened
Out-of-bounds write in Mojo in Google Chrome before 129.0.6668.89 allows remote attackers to corrupt memory via crafted HTML. Mojo insufficiently validates a supplied quantity before a memory write, allowing the operation to exceed its intended bounds; Google has not disclosed the affected function or field. Exploitation requires prior renderer-process compromise, and the published record demonstrates memory corruption rather than a separate code-execution result.
The record
- CVE
- CVE-2024-9369
- Published
- Nov 27, 2024
- Updated
- Nov 20, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-1284, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 27, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 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=129.0.6668.89 <129.0.6668.89
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.
Weakness, pattern, technique
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