CVE-2024-12342 is a critical denial-of-service vulnerability affecting TP-Link VN020 F3v(T) devices running firmware TT_V6.2.1021. The issue is reported in unknown processing of the /control/WANIPConnection endpoint within the device's incomplete SOAP request handler. A crafted or malformed SOAP request to this handler can trigger the flaw and cause the affected device or service to become unavailable. The precise vulnerable function or code path is not provided in the available information.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains two Python scripts (CVE-2024-12342.py and TPLink_DOS_CVE-2024-12342.py) and a README file. Both scripts are designed to exploit CVE-2024-12342, a denial of service vulnerability affecting TP-Link VN020-F3v routers. The main script, CVE-2024-12342.py, sends a SOAP SetConnectionType request with an extremely large string in the <NewConnectionType> field to the device's UPnP WANIPConnection control endpoint, potentially causing the service to crash. The secondary script, TPLink_DOS_CVE-2024-12342.py, sends a SOAP AddPortMapping request to the same endpoint, likely for testing or as an alternative DoS vector. Both scripts require the attacker to specify the target IP and (optionally) port, defaulting to 5431, which is commonly used for UPnP. The exploit is a proof-of-concept and does not provide post-exploitation capabilities. The README provides basic usage instructions. No hardcoded IPs or credentials are present; the scripts are intended for direct targeting of vulnerable devices on the network.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.