dbcve.org
ChromeWeb browser · Google

CVE-2022-2609

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 Nearby Share 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 Nearby Share functionality in Google Chrome on Chrome OS versions prior to 104.0.5112.79. The flaw allows a remote attacker who tricks a user into specific UI interactions to potentially exploit heap corruption through the use-after-free condition.

MitigationUpdate Google Chrome on Chrome OS 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
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. Verify Google Chrome installation
    Check if Google Chrome is installed by looking for the Chrome binary or checking installed packages. On Linux systems, you can use package managers or look for /usr/bin/google-chrome or similar paths.
    Affected if Google Chrome is not installed - no vulnerability applies
  2. Determine installed Chrome version
    Run 'google-chrome --version' or check the package version through your system's package manager (dnf, rpm, etc.)
    Affected if The installed version is lower than 104.0.5112.79 (e.g., 104.0.5112.78 or earlier)
  3. Confirm operating system
    Check the OS version using 'uname -a' or 'cat /etc/os-release'. This vulnerability specifically affects Chrome on Chrome OS, and Fedora 37 packages are also listed as affected.
    Affected if Running Chrome OS or Fedora 37 with a vulnerable Chrome version
  4. Check Nearby Share accessibility
    Verify if the Nearby Share feature is accessible in the Chrome browser. This feature is typically found in Chrome OS settings or Chrome settings on supported platforms.
    Affected if Nearby Share is enabled and accessible - the vulnerability requires this feature to be reachable for exploitation

A user is affected if they are running Google Chrome with a version lower than 104.0.5112.79 on Chrome OS or Fedora 37, and the Nearby Share feature is accessible in their environment.

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.

Recommended fix High confidence

Chrome 104.0.5112.79 or later (stable release)

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Verify the current version is below 104.0.5112.79
  3. Chrome will automatically check for updates; if an update is available, click 'Update Google Chrome'
  4. Restart the browser to complete the update
  5. Alternatively, download the latest stable Chrome from the official website (google.com/chrome) and reinstall to ensure version 104.0.5112.79 or later is applied
  6. For Fedora systems, run 'sudo dnf update google-chrome-stable' 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
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-2609 — 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-2609 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