Heap corruption via File Manager use-after-free
Published Apr 4, 2022 · Updated Aug 2, 2024
Use after free in Google Chrome File Manager on Chrome OS before 98.0.4758.102 allows remote attackers to corrupt heap memory via crafted HTML. The published record establishes stale File Manager object access after deallocation, but the restricted issue does not identify the object or call path. A user must load the attacker-controlled page; the documented consequence is heap corruption, not established code execution.
Summary
What happened
Use after free in Google Chrome File Manager on Chrome OS before 98.0.4758.102 allows remote attackers to corrupt heap memory via crafted HTML. The published record establishes stale File Manager object access after deallocation, but the restricted issue does not identify the object or call path. A user must load the attacker-controlled page; the documented consequence is heap corruption, not established code execution.
The record
- CVE
- CVE-2022-0603
- Published
- Apr 4, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 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 <98.0.4758.102
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