# CVE-2014-7911: Deserialization in n/a

> Attackers can execute arbitrary code on Android devices by sending a malicious intent to system_service, exploiting unsafe deserialization in ObjectInputStream.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xr6p-g44x-qcxm

## What is CVE-2014-7911?

CVE-2014-7911 is a high-severity unsafe deserialization vulnerability in Google Android, published on 15 Dec 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.0 does not verify that deserialization will result in an object that met the requirements for serialization, which allows attackers to execute arbitrary code via a crafted finalize method for a serialized object in an ArrayMap Parcel within an intent sent to system_service, as demonstrated by the finalize method of android.os.BinderProxy, aka Bug 15874291.

Weakness: CWE-264

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

It affects 1 product.


Products: Google Android.

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

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

## Is CVE-2014-7911 being exploited?

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

Public exploit code:

- Local root exploit for Nexus5 Android 4.4.4(KTU84P) (github_poc): https://github.com/retme7/CVE-2014-7911_poc
- exploit for cve-2014-7911; android; java deserialization ;system privilege;ace; (github_poc): https://github.com/GeneBlue/cve-2014-7911-exp
- https://github.com/heeeeen/CVE-2014-7911poc (github_poc): https://github.com/heeeeen/CVE-2014-7911poc
- https://github.com/ele7enxxh/CVE-2014-7911 (github_poc): https://github.com/ele7enxxh/CVE-2014-7911
- CVE-2014-7911 vulnerability and CVE-2014-4322 vulnerability to get root privilege！ (github_poc): https://github.com/koozxcv/CVE-2014-7911-CVE-2014-4322_get_root_privilege
- vulnerabilities‘ Poc and Exploit (github_poc): https://github.com/koozxcv/CVE-2014-7911

## 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-2014-7911 and fix it if it is affected.

What it is: CVE-2014-7911 is a high-severity unsafe deserialization vulnerability in Google Android, published on 15 Dec 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-7911 in the wild and no public exploit code.

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-2014-7911/ (Markdown: https://insights.sbomify.com/CVE-2014-7911/index.md)
```

## Sources

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

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