Memory corruption via Mojo out-of-bounds write
Published Apr 5, 2022 · Updated Aug 2, 2024
Out-of-bounds memory access in Google Chrome before 99.0.4844.51 allows remote attackers to write outside memory bounds via crafted HTML. Mojo processes data reached from the crafted page and writes beyond a valid memory boundary; Google has not disclosed the responsible function or missing check. Exploitation requires a user to open the attacker-controlled page, and the published record establishes memory corruption without a more specific outcome.
Summary
What happened
Out-of-bounds memory access in Google Chrome before 99.0.4844.51 allows remote attackers to write outside memory bounds via crafted HTML. Mojo processes data reached from the crafted page and writes beyond a valid memory boundary; Google has not disclosed the responsible function or missing check. Exploitation requires a user to open the attacker-controlled page, and the published record establishes memory corruption without a more specific outcome.
The record
- CVE
- CVE-2022-0797
- Published
- Apr 5, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=unspecified <99.0.4844.51
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