A stack-based buffer overflow exists in the AgentX::receive_agentx function of the AgentX++ C++ SNMP library (v1.4.16), as used in RealNetworks Helix Server and Helix Mobile Server versions 11.x through 13.x and potentially other products. The flaw allows remote attackers to execute arbitrary code by sending crafted data to the AgentX master port (TCP 705). No authentication is required for exploitation. The vulnerability is confirmed exploitable on Windows systems, where the AgentX master process may run with SYSTEM privileges. Linux systems are not exploitable due to compiler-level stack protections.
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 targeting a stack buffer overflow vulnerability (CVE-2010-1318) in the AgentX++ library as used by Real Networks' Helix Server (master.exe) versions 12 and 13 on Windows. The exploit works by sending a specially crafted sequence of TCP packets to the service listening on port 705, overflowing a stack buffer and allowing arbitrary code execution. The module is operational and allows the attacker to select a Metasploit payload (up to 1024 bytes, with no bad characters), which will be executed with the privileges of the service (typically SYSTEM). The exploit does not work if Data Execution Prevention (NX/XD) is enabled. The code is written in Ruby and follows the standard Metasploit module structure, with all logic contained in a single file. No external endpoints or domains are hardcoded, but the exploit targets the local network service on TCP port 705.
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.