Use after free in Google Chrome
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-416 and the CVSS impact.
Summary
Use after free in WebShare in Google Chrome prior to 99.0.4844.51 allowed a remote attacker who convinced a user to engage in specific user interaction to potentially exploit heap corruption via a crafted HTML page.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
- Fix · CNA Chrome (Google) Fixed in 99.0.4844.51
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Google Chrome 99.0.4844.51
20 records Highest priority Priority MEDIUM 12 MEDIUM, 8 LOW
Other records, highest priority first
- TI-2022-00699 Use after free in Google ChromePriority MEDIUM 43
- TI-2022-00706 Out-of-bounds write in Google ChromePriority MEDIUM 41
- TI-2022-00718 Out-of-bounds write in Google ChromePriority MEDIUM 40
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2022-0794
- 2026-10-03 Alias added: GHSA-ccjf-jgxm-47qc
References
More Google Chrome vulnerabilities
- TI-2025-09686 Type confusion in Google Chrome KEVCVSS 3.1CRITICAL 9.8
- TI-2024-07390 Type confusion in Google Chrome KEVCVSS 3.1CRITICAL 9.6
- TI-2024-04898 Type confusion in Google Chrome KEVCVSS 3.1CRITICAL 9.6
- TI-2024-04600 Type confusion in Google Chrome KEVCVSS 3.1CRITICAL 9.6
- TI-2024-04346 Use after free in Google Chrome KEVCVSS 3.1CRITICAL 9.6
- TI-2023-05824 Integer overflow in Google Chrome KEVCVSS 3.1CRITICAL 9.6
Sources
- CVE-2022-0794 · CVE Program
- CVE-2022-0794 · NVD
- FIRST EPSS
- GHSA-ccjf-jgxm-47qc · GitHub Advisory Database · CC BY 4.0
- CVE-2022-0794 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences