A stack-based buffer overflow exists in the logging function of the Windows Workstation Service (WKSSVC.DLL). Remote attackers can exploit this vulnerability by making RPC calls that result in overly long entries being written to the NetSetup.LOG debug log file. The vulnerability can be triggered, for example, via the NetAddAlternateComputerName API, leading to the execution of arbitrary code in the context of the Workstation Service.
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 contains a single Metasploit module (ms03_049_netapi.rb) that exploits a stack buffer overflow vulnerability in the NetApi32 NetAddAlternateComputerName function of the Workstation service on Windows XP SP0/SP1 (CVE-2003-0812, MS03-049). The exploit connects to the target over SMB, binds to the Workstation service via DCERPC using a named pipe (default 'BROWSER' or 'WKSSVC'), and sends a specially crafted request that overflows a buffer, allowing arbitrary code execution. The payload is customizable and leverages Metasploit's payload framework. The module is operational and requires network access to the target's SMB service. The only file in the repository is a Ruby script structured as a standard Metasploit exploit module.
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.