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

> Buffer overflow in T10 firmware HTTP parser allows attackers to execute arbitrary code or cause 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:** 25 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3c89-xf6c-m942

## What is CVE-2021-43636?

CVE-2021-43636 is a critical memory corruption vulnerability in n/a, published on 25 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Two Buffer Overflow vulnerabilities exists in T10 V2_Firmware V4.1.8cu.5207_B20210320 in the http_request_parse function when processing host data in the HTTP request process.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Totolink T10 V2 Firmware.

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

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

## Is CVE-2021-43636 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-40041](https://insights.sbomify.com/CVE-2023-40041/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-40042](https://insights.sbomify.com/CVE-2023-40042/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-25081](https://insights.sbomify.com/CVE-2022-25081/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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