dbcve.org
ChromeWeb browser · Google

CVE-2021-21134

MEDIUM · 6.5 CVSS v3.1 Published 2021-02-09
Fix available
A fix is available. Upgrade to 88.0.705.50 / 88.0.4324.96 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 Page Info in Google Chrome on iOS prior to 88.0.4324.96 allowed a remote attacker to spoof security UI 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 UI spoofing vulnerability in Google Chrome on iOS where the Page Info dialog can be manipulated via crafted HTML to display incorrect security information, potentially tricking users into believing a site is secure when it is not.

MitigationUpdate Google Chrome on iOS to version 88.0.4324.96 or later to obtain the security fix.

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:< 88.0.4324.96
Edge ChromiumWeb browser
Affected:< 88.0.705.50

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 the browser in use
    Determine whether the browser is Google Chrome on iOS or Microsoft Edge Chromium. On iOS, this can be confirmed by checking the app name in the device settings or app store listing.
    Affected if The browser is Google Chrome on iOS or Microsoft Edge Chromium on iOS
  2. Check the installed version of Google Chrome (iOS)
    Open Google Chrome on the iOS device, tap the three-dot menu, go to Settings, and scroll to the bottom to view the version number, or navigate to chrome://version in the address bar.
    Affected if The installed version is less than 88.0.4324.96
  3. Check the installed version of Microsoft Edge Chromium
    Open Microsoft Edge, tap the three-dot menu, go to Settings, and look for the version number displayed in the app information, or navigate to edge://version in the address bar.
    Affected if The installed version is less than 88.0.705.50

If using Google Chrome on iOS with version below 88.0.4324.96 or Microsoft Edge Chromium with version below 88.0.705.50, the environment is affected by this UI spoofing vulnerability.

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.

From vendor data
Upgrade available Upgrade to 88.0.705.50 / 88.0.4324.96 or later
Fixed in 88.0.705.5088.0.4324.96
Interim mitigation

Update Google Chrome on iOS to version 88.0.4324.96 or later to obtain the security fix.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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