A buffer overflow vulnerability exists in Medal of Honor Allied Assault 1.11v9 and earlier, Breakthrough 2.40b and earlier, and Spearhead 2.15 and earlier. The vulnerability is triggered when the game is played on a Local Area Network (LAN) and can be exploited via specially crafted network packets, such as the getinfo query, connect packet, and potentially other unknown vectors. This allows remote attackers on the same LAN to execute arbitrary code on the affected system.
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 (2 hidden).
This repository contains a single Metasploit module (mohaa_getinfo.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2004-0735) in the 'getinfo' command handler of Medal of Honor Allied Assault v1.0 servers. The exploit works by sending a specially crafted UDP packet to the server's default port (12203/UDP), overflowing the stack and allowing arbitrary code execution. The module is written in Ruby and leverages Metasploit's UDP and payload handling capabilities. The payload is customizable and can be any Metasploit-compatible shellcode (default space: 512 bytes, avoiding null bytes). The exploit is operational and can be used to gain remote code execution on vulnerable game servers. The repository structure is typical for a Metasploit exploit module, with all logic contained in a single Ruby file.
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.