# CVE-2021-32469: Memory corruption in n/a

> An out-of-bounds read in MediaTek Wi-Fi chipsets allows attackers to disclose sensitive information or cause a denial of service via the WPS protocol.

- **Severity:** High 8.2 (`CVSS:3.1/AC:L/AV:N/A:L/C:H/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Dec 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4wgc-5cvv-qf82

## What is CVE-2021-32469?

CVE-2021-32469 is a high-severity memory corruption vulnerability in n/a, published on 25 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MediaTek microchips, as used in NETGEAR devices through 2021-11-11 and other devices, mishandle the WPS (Wi-Fi Protected Setup) protocol. (Affected Chipsets MT7603E, MT7610, MT7612, MT7613, MT7615, MT7620, MT7622, MT7628, MT7629, MT7915 Affected Software Versions 7.4.0.0; Out-of-bounds read).

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 10 products.


Products: Mediatek Mt7603e Firmware, Mediatek Mt7610 Firmware, Mediatek Mt7612 Firmware, Mediatek Mt7613 Firmware, Mediatek Mt7615 Firmware, Mediatek Mt7620 Firmware, Mediatek Mt7622 Firmware, Mediatek Mt7628 Firmware, Mediatek Mt7629 Firmware, Mediatek Mt7915 Firmware.

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

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

## Is CVE-2021-32469 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-32467](https://insights.sbomify.com/CVE-2021-32467/): Memory corruption in n/a (high 8.2)
- [CVE-2021-32468](https://insights.sbomify.com/CVE-2021-32468/): Memory corruption in n/a (high 8.2)
- [CVE-2021-35055](https://insights.sbomify.com/CVE-2021-35055/): Memory corruption in n/a (high 8.2)
- [CVE-2021-37560](https://insights.sbomify.com/CVE-2021-37560/): Memory corruption in n/a (high 8.2)
- [CVE-2021-37561](https://insights.sbomify.com/CVE-2021-37561/): Memory corruption in n/a (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-32469 is a high-severity memory corruption vulnerability in n/a, published on 25 Dec 2021. 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-2021-32469 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-32469/ (Markdown: https://insights.sbomify.com/CVE-2021-32469/index.md)
```

## Sources

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

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