CVE-2022-2610 — Resource Exposure in Google Chrome

CWE-668 — Resource ExposureCWE-667 — Improper Locking7 documents7 sources
Severity
6.5MEDIUMNVD
EPSS
0.4%
top 40.24%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
6
Google ChromeChromiumDebian Chromium+3 more
Timeline
PublishedAug 12
Latest updateAug 22

Description

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.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NExploitability: 2.8 | Impact: 3.6

Affected Packages6 packages

▶CVEListV5google/chromeunspecified — 104.0.5112.79
▶NVDgoogle/chrome< 104.0.5112.79
▶debiandebian/chromium< chromium 104.0.5112.79-1 (bookworm)
▶Debianchromium/chromium< 104.0.5112.79-1~deb11u1+3

Also affects: Fedora 37

🔴Vulnerability Details

2
GHSA
GHSA-v4jr-7w4c-hg9p: Insufficient policy enforcement in Background Fetch in Google Chrome prior to 104↗2022-08-13
▶
OSV
CVE-2022-2610: Insufficient policy enforcement in Background Fetch in Google Chrome prior to 104↗2022-08-12
▶

📋Vendor Advisories

4
Red Hat
kernel: btrfs: get rid of warning on transaction commit when using flushoncommit↗2024-08-22
▶
Microsoft
Chromium: CVE-2022-2610 Insufficient policy enforcement in Background Fetch↗2022-08-09
▶
Chrome
Stable Channel Update for Desktop: CVE-2022-2610↗2022-08-02
▶
Debian
CVE-2022-2610: chromium - Insufficient policy enforcement in Background Fetch in Google Chrome prior to 10...↗2022
▶