CVE-2022-4906: Inappropriate implementation in Blink
Published Nov 8, 2022
·Updated
Inappropriate implementation in Blink in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: High)
Credit
Sergei Glazunov(Google Project Zero)
Affected Software
2 affected componentsFixes available
Google Chrome<108.0.5359.71
108.0.5359.71
Google Chrome<108.0.5359.71
Event History
Nov 8, 2022
CVE Published
12:00 AM
Jul 28, 2023
CVE Published
via MITRE·11:26 PM
Data Sourced
via MITRE·11:26 PM
DescriptionWeakness
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-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
1
What is the severity of CVE-2022-4906?
The severity of CVE-2022-4906 is classified as high.
2
How do I fix CVE-2022-4906?
To fix CVE-2022-4906, update Google Chrome to version 108.0.5359.71 or later.
3
What vulnerability does CVE-2022-4906 describe?
CVE-2022-4906 describes an inappropriate implementation in Blink in Google Chrome that allows remote attackers to perform arbitrary read/write.
4
Which versions of Google Chrome are affected by CVE-2022-4906?
Google Chrome versions prior to 108.0.5359.71 are affected by CVE-2022-4906.
5
Who is the vendor associated with CVE-2022-4906?
The vendor associated with CVE-2022-4906 is Google.