ChromeWeb browser · Google

CVE-2014-7905

MEDIUM · 5.0 CVSS v2.0 Published 2014-11-19
Fix available
A fix is available. Upgrade to after 39.0.2171.45 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Google Chrome before 39.0.2171.65 on Android does not prevent navigation to a URL in cases where an intent for the URL lacks CATEGORY_BROWSABLE, which allows remote attackers to bypass intended access restrictions via a crafted web site.

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

Chrome on Android fails to validate that intents used to navigate to URLs contain the CATEGORY_BROWSABLE flag before allowing navigation. This allows malicious websites to trigger intents that should be restricted, bypassing intended access controls in Android's intent-based security model.

MitigationUpdate Google Chrome for Android to version 39.0.2171.65 or later to include the fix for the missing CATEGORY_BROWSABLE validation.

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:<= 39.0.2171.45

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
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/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 Google Chrome for Android
    Check if Google Chrome is installed on an Android device. This vulnerability only affects Chrome on Android, not desktop Chrome or other browsers.
    Affected if Chrome for Android is not installed on the device, the vulnerability does not apply.
  2. Determine Chrome for Android version
    Open Google Chrome on the Android device, navigate to chrome://version, or go to Settings > Apps > Google Chrome to view the installed version number.
    Affected if The version cannot be determined or Chrome for Android is not found.
  3. Compare version against affected range
    Compare the installed version number to the affected range: version 39.0.2171.45 and earlier. The CVE description indicates versions <= 39.0.2171.45 are affected.
    Affected if The installed version is 39.0.2171.45 or lower.
  4. Verify Android intent handling is in use
    This vulnerability exploits Chrome for Android's intent handling for URLs. The flaw exists when Chrome processes URL intents without validating the CATEGORY_BROWSABLE flag.
    Affected if This is inherent to the affected Chrome for Android versions when handling web links.

You are affected if you are running Google Chrome for Android version 39.0.2171.45 or earlier on an Android device.

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 a release after 39.0.2171.45
Interim mitigation

Update Google Chrome for Android to version 39.0.2171.65 or later to include the fix for the missing CATEGORY_BROWSABLE validation.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-7905 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-7905 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