dbcve.org
ChromeWeb browser · Google

CVE-2022-3201

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-26
Fix available
A fix is available. Upgrade to 105.0.5195.125 or later.
See remediation →
61/100
Remediation priority · Elevated
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
Insufficient validation of untrusted input in DevTools in Google Chrome on Chrome OS prior to 105.0.5195.125 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions 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

This vulnerability in Google Chrome on Chrome OS involves insufficient validation of untrusted input within DevTools. An attacker could bypass navigation restrictions by tricking users into installing a malicious extension and then serving them a crafted HTML page. The attack requires user cooperation (installing a malicious extension) but could allow unauthorized navigation within the browser.

MitigationUpdate Google Chrome to version 105.0.5195.125 or later on Chrome OS devices. Additionally, exercise caution when installing browser extensions and only install from trusted sources.

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.125
FedoraOperating system
Affected:= 37
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
Low
Integrity
Low
Availability
None

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

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 version
    Open chrome://version and look at the 'Chrome' version number, or run 'google-chrome --version' in terminal
    Affected if Version is earlier than 105.0.5195.125
  2. Confirm Chrome OS environment
    Check if the browser is running on Chrome OS by examining the OS identifier in chrome://version or running 'uname -a' to look for 'ChromeOS' or 'chromebook'
    Affected if Running on Chrome OS with a vulnerable Chrome version
  3. Verify the vulnerable DevTools component is accessible
    Open DevTools (F12 or Ctrl+Shift+I) and confirm the DevTools window launches successfully - the vulnerability exists within the DevTools module
    Affected if DevTools is accessible and Chrome version is vulnerable
  4. Check for installed extensions
    Navigate to chrome://extensions, review the list of installed extensions. Look for any unknown, untrusted, or recently added extensions you did not intentionally install
    Affected if Any extension is installed that you did not explicitly trust - the attack requires a malicious extension to be installed

You are affected if you are running Google Chrome with a version earlier than 105.0.5195.125 on Chrome OS and have any browser extension installed, as the exploit requires a malicious extension to be present.

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.125 or later
Fixed in 105.0.5195.125
Interim mitigation

Update Google Chrome to version 105.0.5195.125 or later on Chrome OS devices. Additionally, exercise caution when installing browser extensions and only install from trusted sources.

Recommended fix High confidence

Chrome 105.0.5195.125 or later (also applies to Chromium-based browsers)

  1. Check current Chrome version by navigating to chrome://settings/help or using Menu > Help > About Google Chrome
  2. Update Google Chrome to version 105.0.5195.125 or later by clicking 'Update Google Chrome' if available, or by downloading the latest version from the official Google Chrome website
  3. For Linux systems using distribution packages (Fedora 37, Debian 11), update via package manager: 'sudo dnf update google-chrome-stable' for Fedora or 'sudo apt update && sudo apt upgrade' for Debian
  4. Restart the browser after the update completes
  5. Verify the update was successful by checking chrome://settings/help to confirm the version is 105.0.5195.125 or higher
Caveat Minimal - security updates typically have low risk of breaking changes; users should test extensions after update

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

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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