CVE-2022-4178: Use after free in Mojo
Use after free in Mojo in Google Chrome prior to 108.0.5359.71 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 108.0.5359.71 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 108.0.5359.71-1 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 150.0.7871.100-1~deb12u1Fixed in 156.0.8078.79-1~deb12u1Fixed in 150.0.7871.181-1~deb13u1Fixed in 156.0.8078.79-1~deb13u1Fixed in 156.0.8078.79-1
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-4174
- CVE-2022-4175
- CVE-2022-4176
- CVE-2022-4177
- CVE-2022-4179
- CVE-2022-4180
- CVE-2022-4906
- CVE-2022-4181
- CVE-2022-4907
- CVE-2022-4182
- CVE-2022-4955
- CVE-2022-4183
- CVE-2022-4184
- CVE-2022-4185
- CVE-2022-4186
- CVE-2022-4187
- CVE-2022-4188
- CVE-2022-4189
- CVE-2022-4190
- CVE-2022-4191
- CVE-2022-4192
- CVE-2022-4193
- CVE-2022-4194
- CVE-2022-4195
Frequently Asked Questions
What is the severity of CVE-2022-4178?
The severity of CVE-2022-4178 is classified as High due to potential heap corruption exploitation.
How do I fix CVE-2022-4178?
To fix CVE-2022-4178, update Google Chrome to version 108.0.5359.71 or later.
What causes the vulnerability in CVE-2022-4178?
CVE-2022-4178 is caused by a use after free error in Mojo within Google Chrome.
Can CVE-2022-4178 be exploited remotely?
Yes, CVE-2022-4178 can potentially be exploited remotely if an attacker compromises the renderer process.
Which versions of Google Chrome are affected by CVE-2022-4178?
CVE-2022-4178 affects Google Chrome versions prior to 108.0.5359.71.