dbcve.org
ChromeWeb browser · Google

CVE-2022-3885

HIGH · 8.8 CVSS v3.1 Published 2022-11-09
Fix available
A fix is available. Upgrade to 107.0.5304.106 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 V8 in Google Chrome prior to 107.0.5304.106 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

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

Use-after-free vulnerability in the V8 JavaScript engine in Google Chrome versions prior to 107.0.5304.106. A remote attacker can exploit this by tricking users into visiting a crafted malicious HTML page, potentially leading to heap corruption and arbitrary code execution.

MitigationUpgrade Google Chrome to version 107.0.5304.106 or later. Organizations should deploy browser updates through their patch management infrastructure or have end-users update manually.

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:< 107.0.5304.106
Debian LinuxOperating system
Affected:= 11.0

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 Google Chrome browser version
    Open chrome://version in the Chrome address bar and note the version number listed under 'Google Chrome'
    Affected if The version shown is earlier than 107.0.5304.106 (for example, 106.x.x.x or lower)
  2. Check Chrome version from command line (Windows)
    Run 'reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version' in Command Prompt or PowerShell
    Affected if The reported version value is less than 107.0.5304.106
  3. Check Chrome version from command line (macOS)
    Run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal
    Affected if The output shows a version number lower than 107.0.5304.106
  4. Check Chromium version on Debian Linux
    Run 'dpkg -l | grep chromium' or 'apt show chromium' in Terminal to list the installed Chromium package version
    Affected if The installed chromium or chromium-browser package version is earlier than the version bundled in Chrome 107.0.5304.106 (Debian 11.0 ships Chromium packages that may be affected)
  5. Verify V8 JavaScript engine is active
    In Chrome, navigate to chrome://version and confirm the 'V8' entry is present - this confirms the vulnerable component is loaded
    Affected if V8 is present (which is default in Chrome) - the use-after-free in V8 can be triggered by visiting a malicious page

You are affected if the installed Chrome or Chromium version is less than 107.0.5304.106, as this specific V8 use-after-free vulnerability exists in those earlier 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 107.0.5304.106 or later
Fixed in 107.0.5304.106
Interim mitigation

Upgrade Google Chrome to version 107.0.5304.106 or later. Organizations should deploy browser updates through their patch management infrastructure or have end-users update manually.

Recommended fix High confidence

Chrome 107.0.5304.106 or later

  1. Check current Chrome version by navigating to chrome://settings/help
  2. Update Chrome to version 107.0.5304.106 or later via chrome://settings/help, or download from https://www.google.com/chrome/
  3. Restart Chrome after the update completes
  4. For Debian systems using Chromium browser, wait for Debian security updates (DSA) or consider using the official Google Chrome repository instead
Caveat Standard Chrome update; minor version bump within same major release, minimal risk

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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