Remote heap corruption via shell use after free
Published Jul 25, 2022 · Updated Aug 3, 2024
Use-after-free in Google Chrome on ChromeOS before 100.0.4896.88 allows remote attackers to potentially corrupt heap via crafted HTML. The crafted page reaches shell code that dereferences freed memory, producing heap corruption. Exploitation requires a user to load the crafted page; the record does not establish code execution beyond heap corruption.
Summary
What happened
Use-after-free in Google Chrome on ChromeOS before 100.0.4896.88 allows remote attackers to potentially corrupt heap via crafted HTML. The crafted page reaches shell code that dereferences freed memory, producing heap corruption. Exploitation requires a user to load the crafted page; the record does not establish code execution beyond heap corruption.
The record
- CVE
- CVE-2022-1311
- Published
- Jul 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <100.0.4896.88
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