# CVE-2024-20068: Denial of service in MT6298, MT6813, MT6815, MT6835, MT6878, MT6879, MT6895, MT6895T, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6986, MT6986D, MT6990, MT6991, MT8673, MT8675, MT8771, MT8791T, MT8792, MT8797, MT8798

> Remote attackers can cause a system crash in MediaTek modem firmware via improper input validation, requiring no user interaction or privileges.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jun 2024
- **Updated:** 21 Nov 2024
- **Also known as:** A-332178749, ASB-A-332178749, GHSA-hqvr-h7vg-6665, M-MOLY01270721

## What is CVE-2024-20068?

CVE-2024-20068 is a medium-severity denial of service vulnerability in Mediatek Nr16, published on 3 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service with no additional execution privileges needed. User interaction is no needed for exploitation. Patch ID: MOLY01270721; Issue ID: MSV-1479.

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

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

It affects 2 products.


Products: Mediatek Nr16, Mediatek Nr17.

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

Apply the vendor's patch.

## Is CVE-2024-20068 being exploited?

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

## Other vulnerabilities in Mediatek Nr16

- [CVE-2024-20067](https://insights.sbomify.com/CVE-2024-20067/): Memory corruption in MT6813, MT6815, MT6835, MT6878, MT6897, MT6899, MT6986, MT6986D, MT6991, MT8792 (critical 9.8)
- [CVE-2025-20634](https://insights.sbomify.com/CVE-2025-20634/): Memory corruption in MT2737, MT6813, MT6835, MT6835T, MT6878, MT6878M, MT6879, MT6886, MT6895, MT6895TT, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6983T, MT6985, MT6985T, MT6989, MT6989T, MT6990, MT6991, MT8673, MT8676, MT8678, MT8795T, MT8798, MT8863 (high 8.8)
- [CVE-2024-20066](https://insights.sbomify.com/CVE-2024-20066/): Memory corruption in MT6298, MT6813, MT6815, MT6835, MT6878, MT6879, MT6895, MT6895T, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6986, MT6986D, MT6990, MT6991, MT8673, MT8792, MT8798 (high 7.5)
- [CVE-2024-20151](https://insights.sbomify.com/CVE-2024-20151/): Memory corruption in MT2737, MT2739, MT6789, MT6813, MT6815, MT6835, MT6835T, MT6855, MT6878, MT6878T, MT6879, MT6886, MT6895, MT6895T, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6985, MT6986, MT6986D, MT6988, MT6989, MT6990, MT6991, MT8676, MT8678, MT8798, MT8863 (medium 6.7)
- [CVE-2024-20131](https://insights.sbomify.com/CVE-2024-20131/): Memory corruption in MT2737, MT2739, MT6789, MT6813, MT6815, MT6835, MT6835T, MT6855, MT6878, MT6878T, MT6879, MT6886, MT6895, MT6895T, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6985, MT6986, MT6986D, MT6988, MT6989, MT6990, MT6991, MT8673, MT8676, MT8795T, MT8798 (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20068 and fix it if it is affected.

What it is: CVE-2024-20068 is a medium-severity denial of service vulnerability in Mediatek Nr16, published on 3 Jun 2024. 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-2024-20068 in the wild and no public exploit code.

Affected product: Mediatek Nr16. 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-20068/ (Markdown: https://insights.sbomify.com/CVE-2024-20068/index.md)
```

## Sources

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

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