CVE-2015-6759 json
The shouldTreatAsUniqueOrigin function in platform/weborigin/SecurityOrigin.cpp in Blink, as used in Google Chrome before 46.0.2490.71, doe…
published 11y ago modified 4mo ago also EUVD-2015-6696
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
The shouldTreatAsUniqueOrigin function in platform/weborigin/SecurityOrigin.cpp in Blink, as used in Google Chrome before 46.0.2490.71, does not ensure that the origin of a LocalStorage resource is considered unique, which allows remote attackers to obtain sensitive information via vectors involving a blob: URL.
Patch / fix
- oxide-qt Ubuntu 14.04 LTS 1.10.3-0ubuntu0.14.04.1
- chromium-browser Ubuntu 14.04 LTS 47.0.2526.73-0ubuntu0.14.04.1.1106
ubuntu advisories UBUNTU-CVE-2015-6759
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-browser RHEL 6 EXTRAS 46.0.2490.71-1.el6
red hat advisories RHSA-2015:1912
- 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
Is CVE-2015-6759 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2015-6759 updated cvss 6.4
chromium-browser: Information leakage in LocalStorage
-
Red Hat Enterprise Linux Desktop Supplementary (v. 6) chromium-browser 46.0.2490.71-1.el6 Red Hat Enterprise Linux Server Supplementary (v. 6) chromium-browser 46.0.2490.71-1.el6 Red Hat Enterprise Linux Workstation Supplementary (v. 6) chromium-browser 46.0.2490.71-1.el6fixed: vendor fix RHSA-2015:1912
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.42% chance of exploitation in the next 30 days, higher than 72% 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:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
debian.org
/security/2015/dsa-3376
vendor-advisory
-
security.gentoo.org
/glsa/201603-09
vendor-advisory
-
ubuntu.com
/usn/USN-2770-1
vendor-advisory
-
rhn.redhat.com
/errata/RHSA-2015-1912.html
vendor-advisory
-
ubuntu.com
/usn/USN-2770-2
vendor-advisory
- googlechromereleases.blogspot.com /2015/10/stable-channel-update.html
-
securityfocus.com
/bid/77071
vdb-entry
- src.chromium.org /viewvc/blink?revision=201022&view=revision
- code.google.com /p/chromium/issues/detail?id=514076
-
securitytracker.com
/id/1033816
vdb-entry
Sources
- CVE List CVE-2015-6759
- NVD CVE-2015-6759
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.