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

> A heap buffer overflow in the 2G RRM component allows remote attackers to cause a system crash without user interaction or privileges.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fmc4-4chw-q2xg

## What is CVE-2021-32485?

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

### Official description

In modem 2G RRM, there is a possible system crash due to a heap buffer overflow. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY00500621; Issue ID: ALPS04964926.

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

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

It affects 1 product.


Products: Mediatek Modem.

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

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

## Is CVE-2021-32485 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-32484](https://insights.sbomify.com/CVE-2021-32484/): Memory corruption in n/a (high 7.5)
- [CVE-2021-32486](https://insights.sbomify.com/CVE-2021-32486/): Memory corruption in n/a (high 7.5)
- [CVE-2021-32487](https://insights.sbomify.com/CVE-2021-32487/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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