Heap corruption via Messaging use-after-free
Published Jul 27, 2022 · Updated Aug 3, 2024
Use-after-free in Google Chrome Messaging before 102.0.5005.61 allows remote attackers to trigger heap corruption through crafted HTML. The Messaging component accesses an object after its lifetime has ended; Google has not published the affected function or object lifecycle. A user must load attacker-controlled content, after which the corrupted heap state can crash the renderer or alter browser execution.
Summary
What happened
Use-after-free in Google Chrome Messaging before 102.0.5005.61 allows remote attackers to trigger heap corruption through crafted HTML. The Messaging component accesses an object after its lifetime has ended; Google has not published the affected function or object lifecycle. A user must load attacker-controlled content, after which the corrupted heap state can crash the renderer or alter browser execution.
The record
- CVE
- CVE-2022-1855
- Published
- Jul 27, 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 27, 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 <102.0.5005.61
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