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

> An authenticated remote attacker can execute arbitrary code on TP-Link TL-WR841N routers via a buffer overflow in the httpd daemon.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-h8v9-4xr4-x4xq

## What is CVE-2022-30024?

CVE-2022-30024 is a high-severity memory corruption vulnerability in n/a, published on 14 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A buffer overflow in the httpd daemon on TP-Link TL-WR841N V12 (firmware version 3.16.9) devices allows an authenticated remote attacker to execute arbitrary code via a GET request to the page for the System Tools of the Wi-Fi network. This affects TL-WR841 V12 TL-WR841N(EU)_V12_160624 and TL-WR841 V11 TL-WR841N(EU)_V11_160325 , TL-WR841N_V11_150616 and TL-WR841 V10 TL-WR841N_V10_150310 are also affected.

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

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

It affects 3 products.


Products: Tp-Link Tl-Wr841 Firmware, Tp-Link Tl-Wr841n\(eu\) Firmware, Tp-Link Tl-Wr841n Firmware.

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

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

## Is CVE-2022-30024 being exploited?

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

Public exploit code:

- Tplink wr841 v10 rce exploit (github_poc): https://github.com/ilizavr/CVE-2022-30024

## Other vulnerabilities in n/a

- [CVE-2022-42433](https://insights.sbomify.com/CVE-2022-42433/): Command injection in TL-WR841N (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30024 is a high-severity memory corruption vulnerability in n/a, published on 14 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30024 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-30024/ (Markdown: https://insights.sbomify.com/CVE-2022-30024/index.md)
```

## Sources

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

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