dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Sep 2022. Known ransomware use
ChromeWeb browser · Google

CVE-2022-2294

HIGH · 8.8 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 2.36.5 / 10.15.7 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS 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 WebRTC in Google Chrome prior to 103.0.5060.114 allowed a remote attacker to potentially exploit heap corruption 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 · high confidence

Heap buffer overflow vulnerability in Google Chrome's WebRTC component (prior to v103.0.5060.114). A remote attacker can exploit this by tricking users into visiting a crafted HTML page, potentially leading to heap corruption and arbitrary code execution.

MitigationUpdate Google Chrome to version 103.0.5060.114 or later to patch the vulnerability. Organizations should deploy the browser update through their patch management systems and verify complete coverage.

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:< 103.0.5060.114
FedoraOperating system
Affected:= 35= 36
Extra Packages For Enterprise LinuxApplication
Affected:= 8.0
WebkitgtkWeb browser
Affected:< 2.36.5
Wpe WebkitWeb browser
Affected:< 2.36.5
IpadosOperating system
Affected:< 15.6
Iphone OsOperating system
Affected:< 15.6
Mac Os XOperating system
Affected:< 10.15.7= 10.15.7

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. Check if Google Chrome is installed
    On Windows: Look for Chrome in C:\Program Files\Google\Chrome\Application\ or check Start Menu. On macOS: Look in /Applications/Google Chrome.app. On Linux: Run which google-chrome or check /usr/bin/google-chrome
    Affected if Chrome is installed on the system
  2. Determine installed Chrome version
    On Windows/macOS: Open Chrome, click menu > Help > About Google Chrome. On Linux: Run google-chrome --version or about://version in address bar
    Affected if Version number displayed is below 103.0.5060.114
  3. Verify WebRTC is enabled (required for exploitation)
    In Chrome, go to chrome://settings and search for WebRTC. Check if WebRTC is not explicitly disabled via Group Policy or flags. Also check chrome://webrtc-internals for active WebRTC connections
    Affected if WebRTC is enabled (default state) AND Chrome version is below 103.0.5060.114
  4. Check for other WebKit-based browsers
    If using WebKitGTK or WPEWebKit browsers on Linux (e.g., Epiphany, Midori, etc.), check their versions: webkitgtk --version or wpewebkit --version, or check the package version via package manager (dnf info webkitgtk4 or apt show libwebkit2gtk)
    Affected if WebKitGTK version is below 2.36.5 or WPEWebKit version is below 2.36.5

You are affected if Google Chrome (or a WebKitGTK/WPEWebKit based browser) with WebRTC enabled is installed with a version number less than 103.0.5060.114 (Chrome) or 2.36.5 (WebKit).

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 2.36.5 / 10.15.7 / 15.6 or later
Fixed in 2.36.510.15.715.6
Interim mitigation

Update Google Chrome to version 103.0.5060.114 or later to patch the vulnerability. Organizations should deploy the browser update through their patch management systems and verify complete coverage.

Recommended fix High confidence

Chrome: 103.0.5060.114 | Webkitgtk: 2.36.5 | Wpe Webkit: 2.36.5 | Apple iOS/iPadOS: 15.6

  1. Upgrade Google Chrome to version 103.0.5060.114 or later
  2. For Webkitgtk, upgrade to version 2.36.5 or later
  3. For Wpe Webkit, upgrade to version 2.36.5 or later
  4. For iPadOS, upgrade to version 15.6 or later
  5. For iPhone OS, upgrade to version 15.6 or later
  6. For Mac OS X, apply the Apple security update that addresses this CVE (later than 10.15.7)
  7. For Fedora 35 and 36, apply the Fedora security updates for the WebRTC package
  8. For EPEL 8.0, apply the Extra Packages for Enterprise Linux security updates
Caveat Users should backup important data before upgrading; some legacy extensions or configurations may not be compatible with newer versions

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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-2294 — 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-2294 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