# CVE-2016-2419: Information disclosure in n/a

> Attackers can read sensitive process memory to bypass protections and gain elevated access in Android mediaserver.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mj56-gq69-pp97, UBUNTU-CVE-2016-2419

## What is CVE-2016-2419?

CVE-2016-2419 is a critical vulnerability in Google Android, published on 18 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

media/libmedia/IDrm.cpp in mediaserver in Android 6.x before 2016-04-01 does not initialize a certain key-request data structure, which allows attackers to obtain sensitive information from process memory, and consequently bypass an unspecified protection mechanism, via unspecified vectors, as demonstrated by obtaining Signature or SignatureOrSystem access, aka internal bug 26323455.

Weakness: CWE-264

## Which versions are affected by CVE-2016-2419?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2016-2419?

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

## Is CVE-2016-2419 being exploited?

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

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

What it is: CVE-2016-2419 is a critical vulnerability in Google Android, published on 18 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-2419 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-2016-2419/ (Markdown: https://insights.sbomify.com/CVE-2016-2419/index.md)
```

## Sources

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

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