Skip to content
Fencer Intel
medium 5.0

CVE-2014-7899 json

Google Chrome before 38.0.2125.101 allows remote attackers to spoof the address bar by placing a blob: substring at the beginning of the UR…

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

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

Summary

Google Chrome before 38.0.2125.101 allows remote attackers to spoof the address bar by placing a blob: substring at the beginning of the URL, followed by the original URI scheme and a long username string.

Patch / fix

  • chromium-browser RHEL 6 EXTRAS 39.0.2171.65-2.el6_6

red hat advisories RHSA-2014:1894

  • 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-7899 updated cvss 6.4

chromium-browser: Address bar spoofing

  • Red Hat Enterprise Linux Desktop Supplementary (v. 6) chromium-browser 39.0.2171.65-2.el6_6 Red Hat Enterprise Linux HPC Node Supplementary (v. 6) chromium-browser 39.0.2171.65-2.el6_6 Red Hat Enterprise Linux Server Supplementary (v. 6) chromium-browser 39.0.2171.65-2.el6_6 Red Hat Enterprise Linux Workstation Supplementary (v. 6) chromium-browser 39.0.2171.65-2.el6_6
    fixed: vendor fix RHSA-2014:1894

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.25% chance of exploitation in the next 30 days, higher than 69% 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
  • CWE-20 Improper Input Validation
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.