CVE-2022-1139: Inappropriate implementation in Background Fetch API
Inappropriate implementation in Background Fetch API in Google Chrome prior to 100.0.4896.60 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
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 100.0.4896.60 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 100.0.4896.60-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.
Frequently Asked Questions
What is the severity of CVE-2022-1139?
CVE-2022-1139 is classified as a high severity vulnerability due to its potential to leak cross-origin data.
How do I fix CVE-2022-1139?
To fix CVE-2022-1139, ensure that Google Chrome is updated to version 100.0.4896.60 or later.
Who is affected by CVE-2022-1139?
CVE-2022-1139 affects all users of Google Chrome versions prior to 100.0.4896.60.
What type of attack does CVE-2022-1139 involve?
CVE-2022-1139 involves a remote attacker exploiting the vulnerability via a crafted HTML page.
Can CVE-2022-1139 lead to data breaches?
Yes, CVE-2022-1139 can potentially lead to data breaches by leaking sensitive cross-origin information.