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

> Remote attackers can bypass the Same Origin Policy in Android WebView via crafted null characters, requiring user interaction to execute JavaScript.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/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:** No
- **Published:** 2 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j2q3-jgq8-88q2

## What is CVE-2014-6041?

CVE-2014-6041 is a medium-severity vulnerability in n/a, published on 2 Sep 2014. 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

The Android WebView in Android before 4.4 allows remote attackers to bypass the Same Origin Policy via a crafted attribute containing a \u0000 character, as demonstrated by an onclick="window.open('\u0000javascript: sequence to the Android Browser application 4.2.1 or a third-party web browser.

Weakness: CWE-264

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

It affects 1 product.


Products: Google Android Browser.

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

No fix has been published for CVE-2014-6041 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-6041 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-6041 exists.

Public exploit code:

- Android Open Source Platform (AOSP) Browser UXSS (metasploit)
- Android Browser RCE Through Google Play Store XFO (metasploit)
- Android Open Source Platform (AOSP) Browser UXSS (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-6041 is a medium-severity vulnerability in n/a, published on 2 Sep 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-6041 exists.

Affected product: n/a. 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-6041/ (Markdown: https://insights.sbomify.com/CVE-2014-6041/index.md)
```

## Sources

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

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