dbcve.org
ChromeWeb browser · Google

CVE-2021-37990

MEDIUM · 5.5 CVSS v3.1 Published 2021-11-02
Fix available
A fix is available. Upgrade to 95.0.4638.54 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Inappropriate implementation in WebView in Google Chrome on Android prior to 95.0.4638.54 allowed a remote attacker to leak cross-origin data via a crafted app.

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

Inappropriate implementation in Chrome WebView on Android allowed a malicious app to leak cross-origin data. The WebView failed to properly enforce Same-Origin Policy, enabling a crafted application to access sensitive data from other origins through the browser component.

MitigationUpdate Google Chrome on Android to version 95.0.4638.54 or later to patch the WebView vulnerability. Ensure auto-updates are enabled or push the update via mobile device management (MDM).

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:< 95.0.4638.54
Debian LinuxOperating system
Affected:= 10.0= 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 Chrome version on Android
    Open Chrome on the Android device, navigate to Settings > About Chrome, or run 'adb shell dumpsys package com.android.chrome' via Android Debug Bridge to retrieve the version name and version code.
    Affected if The Chrome version is earlier than 95.0.4638.54 and WebView is using Chrome as the provider.
  2. Verify WebView provider on Android
    Go to Settings > Apps > Default browser app > WebView on the Android device, or check Settings > Developer options > WebView implementation to identify which app provides the WebView functionality.
    Affected if The WebView provider is set to Chrome and its version matches a vulnerable Chrome release.
  3. Check Chrome version on Debian Linux
    Run 'dpkg -l | grep -i chrome' or 'apt-cache policy google-chrome-stable' in the terminal to list the installed Google Chrome package and its version.
    Affected if The installed google-chrome-stable package version is less than 95.0.4638.54.
  4. Confirm WebView is accessible to malicious apps
    Review installed applications on the Android device for any untrusted or unknown apps that could potentially exploit the WebView component, as the vulnerability requires a malicious app to be installed.
    Affected if An untrusted third-party application with internet permissions is present on the device and the WebView version is vulnerable.

A user is affected if their Android device runs Chrome or uses Chrome as the WebView provider with a version before 95.0.4638.54, or if Debian Linux has google-chrome-stable installed with a version earlier than 95.0.4638.54.

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

Update Google Chrome on Android to version 95.0.4638.54 or later to patch the WebView vulnerability. Ensure auto-updates are enabled or push the update via mobile device management (MDM).

Recommended fix High confidence

Chrome 95.0.4638.54 or later

  1. Check current Chromium/Chrome version by navigating to chrome://version or running 'chromium --version' or 'google-chrome --version' in terminal
  2. For Android: Update Chrome to version 95.0.4638.54 or later via Google Play Store
  3. For Linux (Debian): Run 'sudo apt update && sudo apt upgrade' to install the latest Chromium package available in Debian repositories
  4. Alternatively, for Debian 10/11 users, consider installing the latest Chromium from backports or a trusted third-party repository if the official repos don't have the fixed version
  5. Verify the fix by checking that the version now shows 95.0.4638.54 or higher
Caveat Minor version upgrade with no expected breaking changes; however, ensure other browser extensions are compatible

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 / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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