# CVE-2022-33087: Memory corruption in n/a

> Attackers can cause a Denial of Service on TP-Link Archer C50&A5 routers via a crafted HTTP request triggering a stack overflow.

- **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:** 30 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r435-2c6w-hmm5

## What is CVE-2022-33087?

CVE-2022-33087 is a high-severity memory corruption vulnerability in n/a, published on 30 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack overflow in the function DM_ In fillobjbystr() of TP-Link Archer C50&A5(US)_V5_200407 allows attackers to cause a Denial of Service (DoS) via a crafted HTTP request.

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

## Which versions are affected by CVE-2022-33087?

It affects 2 products.


Products: Tp-Link Archer A5 Firmware, Tp-Link Archer C50 Firmware.

## How do I fix CVE-2022-33087?

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

## Is CVE-2022-33087 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-33087 and fix it if it is affected.

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

## Sources

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

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