# CVE-2024-20009: Memory corruption in MT6580, MT6739, MT6761, MT6762, MT6765, MT6779, MT6785, MT6789, MT6833, MT6835, MT6853, MT6853T, MT6855, MT6873, MT6877, MT6879, MT6883, MT6885, MT6886, MT6889, MT6895, MT6983, MT6985, MT8163, MT8167, MT8167S, MT8168, MT8173, MT8175, MT8176, MT8185, MT8188, MT8188T

> A memory corruption flaw in the MediaTek ALAC decoder allows remote attackers to escalate privileges via crafted media files requiring user interaction.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Feb 2024
- **Updated:** 20 Jun 2025
- **Also known as:** A-314698313, ASB-A-314698313, GHSA-2rwq-3mr3-vq32, M-ALPS08441150

## What is CVE-2024-20009?

CVE-2024-20009 is a high-severity memory corruption vulnerability in Google Android, published on 5 Feb 2024. 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

In alac decoder, there is a possible out of bounds write due to an incorrect error handling. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS08441150; Issue ID: ALPS08441150.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-20009?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2024-20009?

Apply the vendor's patch.

## Is CVE-2024-20009 being exploited?

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

What it is: CVE-2024-20009 is a high-severity memory corruption vulnerability in Google Android, published on 5 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-20009 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-2024-20009/ (Markdown: https://insights.sbomify.com/CVE-2024-20009/index.md)
```

## Sources

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

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