# CVE-2021-41789: Denial of service in n/a

> A missing validation check in the WiFi driver allows a proximal attacker to cause a system crash, resulting in remote denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q52m-g3r7-w437

## What is CVE-2021-41789?

CVE-2021-41789 is a medium-severity denial of service vulnerability in n/a, published on 4 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In wifi driver, there is a possible system crash due to a missing validation check. This could lead to remote denial of service from a proximal attacker with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20190426015; Issue ID: GN20190426015.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2021-41789?

It affects 2 products.


Products: Mediatek Mt7615 Firmware, Mediatek Mt7622 Firmware.

## How do I fix CVE-2021-41789?

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

## Is CVE-2021-41789 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41789 and fix it if it is affected.

What it is: CVE-2021-41789 is a medium-severity denial of service vulnerability in n/a, published on 4 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41789 in the wild and no public exploit code.

Affected product: n/a. 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-2021-41789/ (Markdown: https://insights.sbomify.com/CVE-2021-41789/index.md)
```

## Sources

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

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