# CVE-2014-7939: Security feature bypass in n/a

> Remote attackers can bypass Same Origin Policy in Chrome via crafted JavaScript when the Harmony proxy is enabled, requiring user interaction.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m956-r3pg-f666, UBUNTU-CVE-2014-7939

## What is CVE-2014-7939?

CVE-2014-7939 is a medium-severity vulnerability in Google Chrome, published on 22 Jan 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-264

## Which versions are affected by CVE-2014-7939?

It affects 7 products.


Products: Chromium Chromium, Google Chrome, Opensuse Opensuse, Redhat Enterprise Linux Desktop Supplementary, Redhat Enterprise Linux Server Supplementary, Redhat Enterprise Linux Server Supplementary Eus, Redhat Enterprise Linux Workstation Supplementary.

## How do I fix CVE-2014-7939?

Upgrade to a fixed version.

## Is CVE-2014-7939 being exploited?

There is no known exploitation of CVE-2014-7939 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome

- [CVE-2023-1531](https://insights.sbomify.com/CVE-2023-1531/): Use after free in Chrome (high 8.8)
- [CVE-2014-7941](https://insights.sbomify.com/CVE-2014-7941/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-7939 and fix it if it is affected.

What it is: CVE-2014-7939 is a medium-severity vulnerability in Google Chrome, published on 22 Jan 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-7939 in the wild and no public exploit code.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-7939/ (Markdown: https://insights.sbomify.com/CVE-2014-7939/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-7939
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-7939
- OSV: https://osv.dev/vulnerability/CVE-2014-7939

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-7939/
Summaries are generated and may contain mistakes; the official description above is the record.