A stack-based buffer overflow vulnerability exists in AzeoTech DAQFactory 5.85 build 1853 and earlier, a SCADA/HMI product. The flaw resides in the handling of crafted NETB packets sent to the service listening on UDP port 20034. An attacker can exploit this vulnerability remotely to cause a denial of service (crash) or execute arbitrary code on the affected system. The vulnerable feature was undocumented and not believed to be in use by customers.
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 (modules/exploits/windows/scada/daq_factory_bof.rb) that exploits a stack buffer overflow vulnerability (CVE-2011-3492) in Azeotech's DaqFactory Pro 5.85 Build 1853 running on Windows XP SP3. The exploit targets the service listening on UDP port 20034 by sending a specially crafted 'NETB' request, causing a buffer overflow and allowing arbitrary code execution. The module uses an egghunter to locate the payload in memory and requires the attacker to specify the DHCP server IP of the target. The payload is customizable and can be any standard Metasploit Windows payload up to 600 bytes, avoiding null bytes. The exploit leverages a return address in PEGRP32A.dll (jmp esp) to redirect execution. The repository is structured as a typical Metasploit exploit module, written in Ruby, and is operational for real-world exploitation of the specified DaqFactory version.
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.