First published: Thu Jan 22 2015(Updated: )
Google Chrome before 40.0.2214.91, when the Harmony proxy in Google V8 is enabled, allows remote attackers to bypass the Same Origin Policy via crafted JavaScript code with Proxy.create and console.log calls, related to HTTP responses that lack an "X-Content-Type-Options: nosniff" header.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
Google Chrome (Trace Event) | <=40.0.2214.85 | |
Chromium | =40.0.2214.110 | |
Red Hat Enterprise Linux Desktop | =6.0 | |
Red Hat Enterprise Linux Server Supplementary | =6.0 | |
Red Hat Enterprise Linux Server Supplementary EUS | =6.6.z | |
Red Hat Enterprise Linux Workstation Supplementary | =6.0 | |
SUSE Linux | =13.1 | |
SUSE Linux | =13.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-7939 is considered a high severity vulnerability due to its ability to enable bypassing the Same Origin Policy.
To fix CVE-2014-7939, update Google Chrome or Chromium to version 40.0.2214.91 or later.
CVE-2014-7939 affects Google Chrome versions before 40.0.2214.91 and specific versions of Chromium and Red Hat Enterprise Linux.
The impact of CVE-2014-7939 allows remote attackers to execute crafted JavaScript, potentially accessing sensitive information.
A potential workaround for CVE-2014-7939 is to disable the Harmony proxy feature in the V8 JavaScript engine if possible.