dbcve.org
ChromeWeb browser · Google

CVE-2022-2610

MEDIUM · 6.5 CVSS v3.1 Published 2022-08-12
Fix available
A fix is available. Upgrade to 104.0.5112.79 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Background Fetch API in Google Chrome versions prior to 104.0.5112.79 had insufficient policy enforcement that could allow a remote attacker to leak cross-origin data by tricking a user into visiting a specially crafted HTML page.

MitigationUpdate Google Chrome to version 104.0.5112.79 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 104.0.5112.79
FedoraOperating system
Affected:= 37

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome version on desktop
    Navigate to chrome://settings/help or click Menu > Help > About Google Chrome to view the installed version number
    Affected if The displayed version is earlier than 104.0.5112.79 (for example, 103.0.5060.134 or any version in the 100s or 90s series)
  2. Check Chrome package version on Fedora Linux
    Run command: rpm -qa | grep chrome or dnf list installed | grep chrome
    Affected if The installed chrome-beta or google-chrome-stable package version is less than 104.0.5112.79-1
  3. Verify Background Fetch API is accessible
    Open Chrome DevTools (F12), go to Console, and run: 'console.log("Background Fetch" in window)' - this confirms the API exists in the browser
    Affected if Returns true (API is present in the browser, which is the default state in vulnerable versions)
  4. Confirm cross-origin access vulnerability exists
    In a web page context, the vulnerability allows Background Fetch to be invoked from any origin without proper cross-origin restrictions. This is inherent to the vulnerable version - no special config needed.
    Affected if Chrome version is vulnerable and the page can access the Background Fetch API (fetch() calls work across origins without proper isolation)

You are affected if Google Chrome version is below 104.0.5112.79 and the Background Fetch API is accessible to web pages, which is the default state in vulnerable versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 104.0.5112.79 or later
Fixed in 104.0.5112.79
Interim mitigation

Update Google Chrome to version 104.0.5112.79 or later to remediate this vulnerability.

Recommended fix High confidence

Chrome 104.0.5112.79 (or later stable)

  1. Check current Chrome version: open chrome://settings/help or run `google-chrome --version`.
  2. Upgrade Chrome to version 104.0.5112.79 or later (e.g., download from https://www.google.com/chrome/ or use system package manager).
  3. On Fedora 37, run `sudo dnf update google-chrome-stable` to fetch the fixed package.
  4. After update, verify the installed version is >= 104.0.5112.79 (e.g., `google-chrome --version`).
  5. Restart Chrome to apply the fix.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2610 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2610 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data