Heap corruption via Permissions API use-after-free
Published Nov 9, 2022 · Updated Oct 24, 2024
Use after free in Google Chrome's Permissions API before 106.0.5249.119 allows remote attackers to corrupt heap memory via crafted HTML. Public records identify the Permissions API as the locus but do not disclose which object is freed prematurely or subsequently reused. The user must perform specific UI gestures on the crafted page; heap corruption is established, but code execution is not confirmed for this flaw.
Summary
What happened
Use after free in Google Chrome's Permissions API before 106.0.5249.119 allows remote attackers to corrupt heap memory via crafted HTML. Public records identify the Permissions API as the locus but do not disclose which object is freed prematurely or subsequently reused. The user must perform specific UI gestures on the crafted page; heap corruption is established, but code execution is not confirmed for this flaw.
The record
- CVE
- CVE-2022-3448
- Published
- Nov 9, 2022
- Updated
- Oct 24, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 9, 2022CVE publishedPublication date reported by the CVE source.
- Oct 24, 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=0 <106.0.5249.119
- Affected versionversion=unspecified <106.0.5249.119
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