dbcve.org
ChromeWeb browser · Google

CVE-2021-4054

MEDIUM · 6.5 CVSS v3.1 Published 2021-12-23
Fix available
A fix is available. Upgrade to 96.0.4664.93 or later.
See remediation →
72/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
Incorrect security UI in autofill in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to perform domain spoofing 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

This is a security UI flaw in Google Chrome's autofill feature that allows domain spoofing. An attacker can craft a malicious HTML page that tricks the autofill mechanism into displaying a deceptive domain to the user, potentially leading to credential theft or other phishing attacks. The vulnerability exists in versions prior to 96.0.4664.93.

MitigationUpdate Google Chrome to version 96.0.4664.93 or later. For enterprise environments, deploy the update via centralized patch management or group policy.

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:< 96.0.4664.93
FedoraOperating system
Affected:= 34
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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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. Identify if Google Chrome is installed
    Check for Chrome executable. On Windows, look in Program Files\Google\Chrome\Application\ or check for chrome.exe in common paths. On Linux, check /usr/bin/google-chrome or /usr/bin/chromium-browser. On macOS, check /Applications/Google Chrome.app
    Affected if Chrome is not found on the system, this CVE does not apply
  2. Determine installed Chrome version
    Open Chrome, navigate to Settings > About Chrome, or enter chrome://settings/help in the address bar. Alternatively, run 'google-chrome --version' on Linux or check file properties of chrome.exe on Windows
    Affected if The displayed version is earlier than 96.0.4664.93 (for example, 95.x.x.x or earlier)
  3. Verify autofill feature status
    In Chrome, go to Settings > Autofill and passwords, or navigate to chrome://settings/autofill. Check if Autofill forms is toggled on
    Affected if Autofill is enabled - this is required for the spoofing vulnerability to be exploitable. By default, autofill is enabled on most installations

You are affected if Google Chrome is installed with a version prior to 96.0.4664.93 and the autofill feature is enabled.

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

Update Google Chrome to version 96.0.4664.93 or later. For enterprise environments, deploy the update via centralized patch management or group policy.

Recommended fix High confidence

Chrome 96.0.4664.93 or later

  1. Open Google Chrome browser
  2. Navigate to Help > About Google Chrome
  3. Click 'Update Google Chrome' if an update is available
  4. Wait for the update to download and install
  5. Restart the browser to apply the update
  6. Verify the version by returning to Help > About Google Chrome and confirming it shows version 96.0.4664.93 or later
  7. For Linux systems using package managers: Fedora run 'sudo dnf update google-chrome-stable', Debian/Ubuntu run 'sudo apt update && sudo apt upgrade'

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