CVE-2022-4191: Use after free in Sign-In
Use after free in Sign-In in Google Chrome prior to 108.0.5359.71 allowed a remote attacker who convinced a user to engage in specific UI interaction to potentially exploit heap corruption via profile destruction. (Chromium security severity: Medium)
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-4178
- 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-4192
- CVE-2022-4193
- CVE-2022-4194
- CVE-2022-4195
Frequently Asked Questions
What is the severity of CVE-2022-4191?
The severity of CVE-2022-4191 is classified as Medium.
How do I fix CVE-2022-4191?
To fix CVE-2022-4191, update Google Chrome to version 108.0.5359.71 or later.
What causes CVE-2022-4191?
CVE-2022-4191 is caused by a use-after-free vulnerability in the Sign-In feature of Google Chrome.
What impact can CVE-2022-4191 have on users?
CVE-2022-4191 can allow a remote attacker to exploit heap corruption through specific user interactions.
Which versions of Google Chrome are affected by CVE-2022-4191?
Google Chrome versions prior to 108.0.5359.71 are affected by CVE-2022-4191.