dbcve.org
ChromeWeb browser · Google

CVE-2022-2607

HIGH · 8.8 CVSS v3.1 Published 2022-08-12
Fix available
A fix is available. Upgrade to 104.0.5112.79 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Use after free in Tab Strip in Google Chrome on Chrome OS prior to 104.0.5112.79 allowed a remote attacker who convinced a user to engage in specific user interactions to potentially exploit heap corruption via specific UI interactions.

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 · high confidence

A use-after-free vulnerability exists in the Tab Strip component of Google Chrome on Chrome OS before version 104.0.5112.79. The flaw allows a remote attacker to potentially exploit heap corruption by tricking users into performing specific UI interactions with the tab strip, leading to memory corruption that could be leveraged for code execution.

MitigationUpdate Google Chrome on Chrome OS to version 104.0.5112.79 or later to remediate this vulnerability. Organizations should deploy browser updates through their patch management infrastructure and verify completion across affected endpoints.

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
High
Availability
High

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

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. Identify Google Chrome installation
    Check if Google Chrome is installed on the system by looking for the Chrome executable or checking the browser version through the UI (navigate to chrome://version) or command line (chrome --version or similar)
    Affected if Google Chrome is not installed or cannot be found on the system
  2. Determine installed Chrome version
    Navigate to chrome://version in the browser address bar or run the Chrome version command from a terminal, then compare the displayed version number to 104.0.5112.79
    Affected if The installed version is lower than 104.0.5112.79 (for example, 104.0.5112.78 or earlier)
  3. Verify operating system platform
    Check whether the Chrome browser is running on Chrome OS or Fedora 37 by examining the system information (in Chrome, go to chrome://system or check the OS name in the system settings)
    Affected if The system is running Chrome OS or Fedora 37 and the Chrome version is below 104.0.5112.79
  4. Confirm tab strip accessibility
    Verify that the Tab Strip feature is accessible in the browser by opening multiple tabs and confirming the tab strip UI is visible and functional in the Chrome OS interface
    Affected if The user can interact with the tab strip on Chrome OS or Fedora 37 and the Chrome version is below 104.0.5112.79

The environment is affected if Google Chrome on Chrome OS or Fedora 37 is installed with a version lower than 104.0.5112.79 and the tab strip UI feature is accessible.

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 on Chrome OS to version 104.0.5112.79 or later to remediate this vulnerability. Organizations should deploy browser updates through their patch management infrastructure and verify completion across affected endpoints.

Recommended fix High confidence

Chrome 104.0.5112.79 or later

  1. Update Google Chrome to version 104.0.5112.79 or later. On desktop systems, Chrome typically auto-updates; to force an update, go to Chrome Menu > Help > About Google Chrome and verify the version number.
  2. For Fedora 37 systems: Run `sudo dnf update google-chrome-stable` once the fixed package is available in the Fedora repositories to receive the security patch.

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2607 — 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-2607 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