dbcve.org
ChromeWeb browser · Google

CVE-2022-3050

HIGH · 8.8 CVSS v3.1 Published 2022-09-26
Fix available
A fix is available. Upgrade to 105.0.5195.52 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
Heap buffer overflow in WebUI in Google Chrome on Chrome OS prior to 105.0.5195.52 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via crafted 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

Heap buffer overflow vulnerability in the WebUI component of Google Chrome on Chrome OS versions prior to 105.0.5195.52. A remote attacker tricks users into performing specific UI interactions, allowing crafted UI interactions to trigger heap corruption. The attack requires social engineering to induce user interaction rather than being remotely exploitable without user action.

MitigationUpdate Google Chrome on Chrome OS to version 105.0.5195.52 or later. In enterprise environments, deploy the update via centralized patch management and verify successful remediation across all affected devices.

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:< 105.0.5195.52
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. Confirm Google Chrome or Chromium is installed
    On Chrome OS: Open chrome://settings/help or go to Settings > About Chrome. On Linux/Fedora: Run `google-chrome --version` or `chromium-browser --version` in terminal.
    Affected if No browser is found, this CVE does not apply.
  2. Identify the exact browser version
    Navigate to chrome://settings/help in the browser URL bar. The version number is displayed on that page.
    Affected if The version number shown is the installed version to compare.
  3. Compare installed version against the vulnerable range
    Compare the installed version number to 105.0.5195.52. Versions below 105.0.5195.52 are affected.
    Affected if Installed version is less than 105.0.5195.52 (for example, 105.0.5195.51, 104.x.x.x, etc.).
  4. Check operating system context
    Verify the OS is Chrome OS or Fedora 37 by checking System Settings > About or running `cat /etc/os-release` on Linux.
    Affected if Running Chrome on Chrome OS or Fedora 37 specifically.
  5. Verify WebUI component is accessible
    Navigate to any chrome:// URL (such as chrome://settings, chrome://extensions, or chrome://flags) in the browser.
    Affected if WebUI pages load successfully, confirming the WebUI component is enabled (which is default in Chrome).

You are affected if Google Chrome or Chromium version is less than 105.0.5195.52 on Chrome OS or Fedora 37, and the WebUI component is accessible (default state).

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 105.0.5195.52 or later
Fixed in 105.0.5195.52
Interim mitigation

Update Google Chrome on Chrome OS to version 105.0.5195.52 or later. In enterprise environments, deploy the update via centralized patch management and verify successful remediation across all affected devices.

Recommended fix High confidence

Chrome 105.0.5195.52 or later

  1. Check current Chrome version by navigating to chrome://settings/help
  2. Update Chrome to version 105.0.5195.52 or later via the browser's built-in update mechanism or by downloading from the official Chrome download page
  3. Restart Chrome after the update completes
  4. Verify the installed version is 105.0.5195.52 or higher

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 / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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