CVE-2022-4925: Insufficient validation of untrusted input in QUIC
Published Aug 10, 2021
·Updated
Insufficient validation of untrusted input in QUIC in Google Chrome prior to 97.0.4692.71 allowed a remote attacker to perform header splitting via malicious network traffic. (Chromium security severity: Low)
Credit
Youssef Sammouda
Affected Software
2 affected componentsFixes available
Google Chrome<97.0.4692.71
97.0.4692.71
Google Chrome<97.0.4692.71
Event History
Aug 10, 2021
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-0096
- CVE-2022-0097
- CVE-2022-0098
- CVE-2022-0099
- CVE-2022-0100
- CVE-2022-0101
- CVE-2022-0337
- CVE-2022-0102
- CVE-2022-0103
- CVE-2022-4924
- CVE-2022-0104
- CVE-2022-0105
- CVE-2022-0106
- CVE-2022-0107
- CVE-2022-0108
- CVE-2022-0109
- CVE-2022-0110
- CVE-2022-0111
- CVE-2022-0112
- CVE-2022-0113
- CVE-2022-0114
- CVE-2022-0115
- CVE-2022-0116
- CVE-2022-0117
- CVE-2022-0118
- CVE-2022-0120
Frequently Asked Questions
1
What is the severity of CVE-2022-4925?
The severity of CVE-2022-4925 is classified as low.
2
How do I fix CVE-2022-4925?
To fix CVE-2022-4925, update Google Chrome to version 97.0.4692.71 or later.
3
What causes CVE-2022-4925?
CVE-2022-4925 is caused by insufficient validation of untrusted input in QUIC in Google Chrome.
4
Who is affected by CVE-2022-4925?
Users of Google Chrome versions prior to 97.0.4692.71 are affected by CVE-2022-4925.
5
Can CVE-2022-4925 be exploited remotely?
Yes, CVE-2022-4925 allows a remote attacker to perform header splitting via malicious network traffic.