Loading vulnerability…
A vulnerability in the WINS service (wins.exe) on Microsoft Windows NT Server 4.0, Windows 2000 Server, and Windows Server 2003 allows remote attackers to write to arbitrary memory locations. The flaw is triggered by sending a specially crafted WINS replication packet to TCP port 42, which manipulates a memory pointer, potentially leading to 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 (1 hidden).
This repository contains a single Metasploit module (ms04_045_wins.rb) that exploits an arbitrary memory write vulnerability (CVE-2004-1080) in the Microsoft WINS service on Windows 2000. The exploit targets systems running the WINS service on TCP port 42 and is capable of executing arbitrary code with system privileges. The module includes routines for fingerprinting the target system to determine OS and service pack, and only attempts exploitation if the system appears vulnerable (Windows 2000 SP0, SP2, SP3, or SP4). The payload is customizable and leverages Metasploit's payload framework, allowing for a variety of post-exploitation actions. The code is written in Ruby and is structured as a standard Metasploit exploit module, making it easy to use within the Metasploit framework. No hardcoded IP addresses or URLs are present; the only fingerprintable endpoint is the use of TCP port 42, which is the default port for the WINS service.
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.
1 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.