Loading vulnerability…
A stack-based buffer overflow exists in doexec.c in Netcat for Windows 1.1 when the application is run with the -e option. The vulnerability is triggered by sending a long DNS command, which overflows a stack buffer and allows for the execution of arbitrary code.
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 a single Metasploit exploit module targeting a stack buffer overflow vulnerability in Netcat v1.10 NT (CVE-2004-1317) on Windows. The exploit works by sending a specially crafted, overly long string to a Netcat instance that is running with the '-L -p <port> -e <executable>' options, causing a buffer overflow and allowing arbitrary code execution via SEH overwrite. The module is written in Ruby and leverages the Metasploit framework's payload system, allowing the attacker to inject a customizable payload (up to 236 bytes, avoiding certain bad characters). The exploit is operational and has been tested on various Windows versions. The main attack vector is network-based, targeting the TCP port where Netcat is listening (example: port 31337). The only file in the repository is the Metasploit module itself, and it is structured according to standard Metasploit conventions.
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.