ChromeWeb browser · Google
CVE-2021-30580
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 · uneditedInsufficient policy enforcement in Android intents in Google Chrome prior to 92.0.4515.107 allowed an attacker who convinced a user to install a malicious application to obtain potentially sensitive information 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 confidenceInsufficient policy enforcement in Chrome's Android intent handling allows a malicious application installed on the same device to trigger Chrome via crafted HTML pages and potentially exfiltrate sensitive information. The vulnerability stems from Chrome not properly restricting what data can be accessed or returned through Android intent URLs processed by the browser.
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
< 92.0.4515.107
FedoraOperating system
= 33= 34= 35CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Chrome for Android installationOpen Chrome on your Android device, tap the three-dot menu, then go to Settings > About Chrome to view the installed version numberAffected if Chrome for Android is installed and the displayed version is lower than 92.0.4515.107
-
Compare version against vulnerable rangeNote the version shown in About Chrome (format typically xx.x.xxxxx.xx) and compare numerically to 92.0.4515.107 - any version below this threshold is affectedAffected if The installed version string is less than 92.0.4515.107 (for example, 91.0.4472.101 would be vulnerable)
-
Check for untrusted applicationsReview all installed applications on the device, particularly those installed from sources other than the official Google Play Store - look for unfamiliar or suspicious applications that could craft malicious intent URLsAffected if Any untrusted or unknown third-party applications are installed on the same device that could potentially invoke Chrome via intent URLs
-
Verify application install sources (Android)On the Android device, go to Settings > Apps > Menu > Special access > Install unknown apps - review which apps have permission to install other appsAffected if Applications from unknown sources are enabled, increasing the risk of a malicious app being installed
You are affected if Chrome for Android version is below 92.0.4515.107 AND a potentially malicious application exists on the same device that could trigger Chrome via crafted intent URLs.
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.
From vendor data92.0.4515.107
Update Google Chrome for Android to version 92.0.4515.107 or later. Users should also exercise caution when installing applications from unknown sources, as this attack requires a malicious app to be pre-installed on the device.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30580 — 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-30580 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