Loading vulnerability…
A stack-based buffer overflow exists in MDMUtil.dll, used by MDMTool.exe in Moxa Device Manager MDM Tool versions prior to 2.3. The vulnerability can be triggered by sending specially crafted data to a session on TCP port 54321, allowing a remote MDM Gateway to exploit the flaw.
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.
This repository contains a single Metasploit module (modules/exploits/windows/scada/moxa_mdmtool.rb) that exploits a stack buffer overflow vulnerability (CVE-2010-4741) in MOXA Device Manager Tool 2.1 for Windows. The exploit works by running a TCP server (default port 54321) and waiting for a connection from the vulnerable client. Upon connection, it sends a specially crafted response that overflows a stack buffer, overwrites SEH, and injects arbitrary shellcode (payload) into the target process. The payload is customizable via Metasploit and can provide remote code execution on the target system. The module is operational and leverages Metasploit's payload and handler infrastructure. The only fingerprintable endpoint is the TCP port (default 54321) that the exploit listens on. The code is written in Ruby and is 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.