# CVE-2013-4710: Code injection in n/a

> Remote attackers can execute arbitrary Java methods or cause device reboots via crafted web pages exploiting Android WebView implementation flaws.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 3 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-99c2-83v2-365x

## What is CVE-2013-4710?

CVE-2013-4710 is a critical code injection vulnerability in Google Android, published on 3 Mar 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

Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly implement the WebView class, which allows remote attackers to execute arbitrary methods of Java objects or cause a denial of service (reboot) via a crafted web page, as demonstrated by use of the WebView.addJavascriptInterface method, a related issue to CVE-2012-6636.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-4710?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2013-4710?

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

## Is CVE-2013-4710 being exploited?

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

Public exploit code:

- Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly implement the WebView class, which allows remote attackers to execute arbitrary methods of Java objects or cause a denial of service (reboot) via a crafted web page, as demonstrated by use of the WebView.addJavascriptInterface method, a related issue to CVE-2012-6636. (github_poc): https://github.com/Snip3R69/CVE-2013-4710-WebView-RCE-Vulnerability
- Google Android 4.2 Browser and WebView - 'addJavascriptInterface' Code Execution (Metasploit) (exploitdb)
- Android Browser and WebView addJavascriptInterface Code Execution (metasploit)
- Android Browser and WebView addJavascriptInterface - Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4710 and fix it if it is affected.

What it is: CVE-2013-4710 is a critical code injection vulnerability in Google Android, published on 3 Mar 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-2013-4710 exists.

Affected product: Google Android. 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-2013-4710/ (Markdown: https://insights.sbomify.com/CVE-2013-4710/index.md)
```

## Sources

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

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