Heap corruption via notification use-after-free
Published Nov 1, 2022 · Updated Aug 3, 2024
Use-after-free in ChromeOS Notifications in Google Chrome before 106.0.5249.62 allows remote attackers to corrupt heap memory through UI interaction. Google identifies the affected locus as ChromeOS Notifications but has not published which object is freed or how the interface later dereferences it. Exploitation requires user interaction followed by a ChromeOS reboot; public records do not identify a consequence beyond heap corruption.
Summary
What happened
Use-after-free in ChromeOS Notifications in Google Chrome before 106.0.5249.62 allows remote attackers to corrupt heap memory through UI interaction. Google identifies the affected locus as ChromeOS Notifications but has not published which object is freed or how the interface later dereferences it. Exploitation requires user interaction followed by a ChromeOS reboot; public records do not identify a consequence beyond heap corruption.
The record
- CVE
- CVE-2022-3318
- Published
- Nov 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-404
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 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 <106.0.5249.62
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.
Weakness, pattern, technique
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