# CVE-2015-3864: Integer overflow in n/a

> Remote attackers can execute arbitrary code on Android devices by tricking users into opening malicious MPEG-4 files, exploiting an integer underflow in the media server.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 1 Oct 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9pwf-jxj3-pf4m

## What is CVE-2015-3864?

CVE-2015-3864 is a critical vulnerability in Google Android, published on 1 Oct 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

Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in Android before 5.1.1 LMY48M allows remote attackers to execute arbitrary code via crafted MPEG-4 data, aka internal bug 23034759.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-3824.

Weakness: CWE-189

## Which versions are affected by CVE-2015-3864?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2015-3864?

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

## Is CVE-2015-3864 being exploited?

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

Public exploit code:

- Python script to generate a malicious MP4 file and start a CherryPy web server hosting a simple HTML page with the embedded file.  Exploits another Stagefright vulnerability, the integer overflow (CVE-2015-3864). (github_poc): https://github.com/eudemonics/scaredycat
- PoC - Binary patches for CVE-2015-3864 (NOT for production, use at your own risk) (github_poc): https://github.com/pwnaccelerator/stagefright-cve-2015-3864
- Android Stagefright MP4 tx3g Integer Overflow (metasploit)
- Google Android - libstagefright Integer Overflow Remote Code Execution (exploitdb)
- Google Android 5.0.1 - Metaphor Stagefright (ASLR Bypass) (exploitdb)
- Google Android 5.0 < 5.1.1 - 'Stagefright' .MP4 tx3g Integer Overflow (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-2015-3864 and fix it if it is affected.

What it is: CVE-2015-3864 is a critical vulnerability in Google Android, published on 1 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-3864 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-2015-3864/ (Markdown: https://insights.sbomify.com/CVE-2015-3864/index.md)
```

## Sources

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

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