ChromeWeb browser · Google
CVE-2021-30506
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 · uneditedIncorrect security UI in Web App Installs in Google Chrome on Android prior to 90.0.4430.212 allowed an attacker who convinced a user to install a web application to inject scripts or HTML into a privileged page 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 confidenceThis is a UI-based security flaw in Google Chrome on Android's Web App Install feature (versions prior to 90.0.4430.212). The incorrect security UI allows a malicious crafted web page to inject scripts or HTML into privileged pages when a user is convinced to install a malicious web application, bypassing the intended security boundaries through UI confusion.
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
< 90.0.4430.212
FedoraOperating system
= 33= 34CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Google Chrome is installed on AndroidOpen Android Settings > Apps > Chrome, or check the Chrome app version from the Play Store or app info screenAffected if Chrome browser is installed on the Android device
-
Determine the installed Chrome version on AndroidNavigate to Chrome > Settings > About Chrome, or view the version in the app's package informationAffected if The version shown is less than 90.0.4430.212 (e.g., 90.0.4430.211 or earlier)
-
Verify the Web App Install feature is accessibleConfirm Chrome has permissions to install web apps and the feature is not disabled by enterprise policy or MDMAffected if The Web App Install feature is enabled and the Chrome version is vulnerable
-
For Fedora desktop systems, check installed Chrome packageRun `rpm -qa | grep -i chrome` or check installed packages via PackageKit to see if Google Chrome from Fedora repos is installedAffected if Chrome packages from Fedora 33 or 34 repositories are installed
A user is affected if Google Chrome for Android is installed with a version prior to 90.0.4430.212 and the Web App Install feature is accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped90.0.4430.212
Update Google Chrome for Android to version 90.0.4430.212 or later. Organizations should ensure mobile device management policies enforce browser updates.
Chrome 90.0.4430.212 or later
- For Chrome on Android: Open Google Play Store and update Chrome to version 90.0.4430.212 or later
- For Fedora desktop systems: Run 'sudo dnf update google-chrome-stable' to install the patched version
- Alternatively, download the latest Chrome version from the official Chrome download page: https://www.google.com/chrome/
- After updating, verify the version by navigating to chrome://settings/help in the address bar
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2021-30506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-30506 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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