CVE-2022-2610: Insufficient policy enforcement in Background Fetch
Published Dec 9, 2021
·Updated
Insufficient policy enforcement in Background Fetch in Google Chrome prior to 104.0.5112.79 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Credit
Maurice Dauer
Affected Software
3 affected componentsFixes available
Google Chrome<104.0.5112.79
104.0.5112.79
Google Chrome<104.0.5112.79
fedoraproject fedora=37
Event History
Dec 9, 2021
CVE Published
12:00 AM
Aug 12, 2022
CVE Published
via MITRE·07:36 PM
Data Sourced
via MITRE·07:36 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-2603
- CVE-2022-2604
- CVE-2022-2605
- CVE-2022-2606
- CVE-2022-2607
- CVE-2022-2608
- CVE-2022-2609
- CVE-2022-2742
- CVE-2022-2743
- CVE-2022-2611
- CVE-2022-2612
- CVE-2022-2613
- CVE-2022-2614
- CVE-2022-4914
- CVE-2022-2615
- CVE-2022-2616
- CVE-2022-2617
- CVE-2022-2618
- CVE-2022-2619
- CVE-2022-2620
- CVE-2022-2621
- CVE-2022-2622
- CVE-2022-2623
- CVE-2022-2624
Frequently Asked Questions
1
What is the severity of CVE-2022-2610?
CVE-2022-2610 has a severity rating of high due to its potential for cross-origin data leakage.
2
How do I fix CVE-2022-2610?
To fix CVE-2022-2610, update Google Chrome to version 104.0.5112.79 or later.
3
What type of vulnerability is CVE-2022-2610?
CVE-2022-2610 is classified as an insufficient policy enforcement vulnerability.
4
Which software versions are affected by CVE-2022-2610?
CVE-2022-2610 affects Google Chrome versions prior to 104.0.5112.79 and Fedora version 37.
5
What could an attacker achieve by exploiting CVE-2022-2610?
An attacker exploiting CVE-2022-2610 could leak sensitive cross-origin data from victims using a crafted HTML page.