Heap corruption via MediaStream use-after-free
Published Apr 5, 2022 · Updated Aug 2, 2024
Use-after-free in Google Chrome MediaStream before 99.0.4844.51 allows attackers to corrupt heap memory through a crafted extension. The public record identifies MediaStream but does not disclose which object is freed prematurely or which later operation reuses it. Exploitation requires convincing a user to install a malicious extension; the documented consequence is heap corruption, not a published sandbox escape.
Summary
What happened
Use-after-free in Google Chrome MediaStream before 99.0.4844.51 allows attackers to corrupt heap memory through a crafted extension. The public record identifies MediaStream but does not disclose which object is freed prematurely or which later operation reuses it. Exploitation requires convincing a user to install a malicious extension; the documented consequence is heap corruption, not a published sandbox escape.
The record
- CVE
- CVE-2022-0798
- Published
- Apr 5, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1176
- 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