Skip to content
Fencer Intel
medium 5.0

CVE-2014-7905 json

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_BROWS…

published 2014-11-19 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-7755

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

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.

Patch / fix

  • chromium-browser Ubuntu 14.04 LTS 39.0.2171.65-0ubuntu0.14.04.1.1064

ubuntu advisories UBUNTU-CVE-2014-7905

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • chromium openSUSE Tumbleweed 55.0.2883.75-3.1
  • chromium openSUSE Tumbleweed 113.0.5672.92-1.1

opensuse advisories openSUSE-SU-2024:10171-1openSUSE-SU-2024:12948-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-7905 updated cvss 4.0

chromium-browser: Flaw allowing navigation to intents that do not have the BROWSABLE category

  • Red Hat Enterprise Linux 6 chromium-browser
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.06% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.