# CVE-2021-30636: Integer overflow in n/a

> An integer overflow in MediaTek LinkIt SDK memory allocation functions can lead to memory corruption, potentially allowing code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gc9h-g4qm-fgcv

## What is CVE-2021-30636?

CVE-2021-30636 is a critical vulnerability in n/a, published on 24 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In MediaTek LinkIt SDK before 4.6.1, there is a possible memory corruption due to an integer overflow during mishandled memory allocation by pvPortCalloc and pvPortRealloc.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Mediatek Linkit Software Development Kit.

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

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

## Is CVE-2021-30636 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-32665](https://insights.sbomify.com/CVE-2022-32665/): Command injection in EN7528, EN7580 (critical 9.8)
- [CVE-2022-32664](https://insights.sbomify.com/CVE-2022-32664/): Command injection in EN7516, EN7528, EN7529, EN7561, EN7562, EN7580 (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-30636 is a critical vulnerability in n/a, published on 24 Jan 2022. 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-30636 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-30636/ (Markdown: https://insights.sbomify.com/CVE-2021-30636/index.md)
```

## Sources

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

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