Loading vulnerability…
Stormy Studios Knet 1.04c and earlier contains a buffer overflow in its handling of HTTP GET requests. A remote attacker can submit an excessively long HTTP GET request to trigger the flaw, causing denial of service and potentially achieving arbitrary code execution.
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 (3 hidden).
This repository is a small standalone exploit repo containing a README and a single Python script, knet_exploit.py. The README identifies the target as CVE-2005-0575 affecting KNet Web Server 1.04b and notes that the exploit may require adjustment before use. The Python script is the full exploit implementation. The exploit is a remote network/web attack against a vulnerable HTTP service. It constructs an oversized HTTP GET request intended to trigger an SEH-based buffer overflow in KNet Web Server 1.04b. The payload layout includes a large NOP sled, embedded x86 shellcode prefixed with the egg marker 'T00WT00W', a 32-byte egghunter, and NSEH/SEH overwrite values. The shellcode is explicitly described in comments as a 344-byte bind shell on TCP/4444. Operationally, the script connects to a hardcoded target at 10.200.0.120 on port 80, sends the malicious HTTP request, waits 10 seconds, and then runs 'telnet 10.200.0.120 4444' to access the spawned shell. This indicates the exploit is not just a proof of concept crash script; it is intended to achieve remote code execution with an interactive post-exploitation channel. However, it is still basic and hardcoded rather than modular or framework-integrated, so OPERATIONAL is the best maturity fit. Notable fingerprintable observables are the target IP 10.200.0.120, the exploit delivery service on TCP/80, the bind shell on TCP/4444, and the use of an HTTP GET request with a Host header set to the same IP. There are no external C2 servers, download URLs, registry keys, or persistence mechanisms in the code.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.