# CVE-2024-12342: TP-Link VN020 F3v(T) Incomplete SOAP Request WANIPConnection denial of service

> A local network attacker can cause a denial of service in TP-Link VN020 F3v(T) devices via incomplete SOAP requests.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2024
- **Updated:** 9 Dec 2024
- **Also known as:** GHSA-5qx6-f8xw-vj8f

## What is CVE-2024-12342?

CVE-2024-12342 is a high-severity denial of service vulnerability in TP-Link VN020 F3v(T), published on 8 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in TP-Link VN020 F3v(T) TT_V6.2.1021. It has been rated as critical. This issue affects some unknown processing of the file /control/WANIPConnection of the component Incomplete SOAP Request Handler. The manipulation leads to denial of service. The attack can only be initiated within the local network. The exploit has been disclosed to the public and may be used.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2024-12342?


## How do I fix CVE-2024-12342?

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

## Is CVE-2024-12342 being exploited?

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

Public exploit code:

- TP-Link VN020 F3v(T) TT_V6.2.1021 - Denial Of Service (DOS) (exploitdb)
- TPLink VN020-F3v Denial of Service (CVE-2024-12342) (github_poc): https://github.com/becrevex/TPLink-VN020-DoS

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12342 and fix it if it is affected.

What it is: CVE-2024-12342 is a high-severity denial of service vulnerability in TP-Link VN020 F3v(T), published on 8 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12342 in the wild and no public exploit code.

Affected product: TP-Link VN020 F3v(T). 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-2024-12342/ (Markdown: https://insights.sbomify.com/CVE-2024-12342/index.md)
```

## Sources

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

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