# CVE-2020-8899: Memory corruption in Quram library when decoding qmg can lead to RCE

> An attacker can achieve remote code execution on Samsung Android devices by sending a malicious MMS, exploiting a heap overflow in the Quram library.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6qjj-3q9g-g44p

## What is CVE-2020-8899?

CVE-2020-8899 is a critical memory corruption vulnerability in Google Android, published on 6 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a buffer overwrite vulnerability in the Quram qmg library of Samsung's Android OS versions O(8.x), P(9.0) and Q(10.0). An unauthenticated, unauthorized attacker sending a specially crafted MMS to a vulnerable phone can trigger a heap-based buffer overflow in the Quram image codec leading to an arbitrary remote code execution (RCE) without any user interaction. The Samsung ID is SVE-2020-16747.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2020-8899?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2020-8899?

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

## Is CVE-2020-8899 being exploited?

There is no known exploitation of CVE-2020-8899 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-2020-8899 and fix it if it is affected.

What it is: CVE-2020-8899 is a critical memory corruption vulnerability in Google Android, published on 6 May 2020. 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-2020-8899 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-2020-8899/ (Markdown: https://insights.sbomify.com/CVE-2020-8899/index.md)
```

## Sources

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

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