Loading vulnerability…
TrackerCam 5.12 and earlier are vulnerable to multiple buffer overflow conditions. Specifically, a remote attacker can trigger a buffer overflow by sending an HTTP request with an excessively long User-Agent header or by supplying a long argument to an arbitrary PHP script handled by the application. These flaws are due to insufficient bounds checking on user-supplied input.
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 (trackercam_phparg_overflow.rb) that exploits a stack buffer overflow vulnerability (CVE-2005-0478) in the TrackerCam web server for Windows. The exploit targets the 'userID' parameter of the /tuner/TunerGuide.php3 endpoint, allowing remote code execution with the privileges of the web server process. The module also leverages a directory traversal flaw via /tuner/ComGetLogFile.php3 to fingerprint the system and determine the Windows version by reading files such as boot.ini. The exploit is operational, providing customizable Metasploit payload delivery, and is effective against Windows 2000, Windows XP (SP0/SP1), and Windows NT 4.0 (SP4/SP5/SP6) systems running the vulnerable TrackerCam web server. The code is written in Ruby and is structured as a standard Metasploit exploit module, with clear separation of fingerprinting, exploitation, and payload delivery logic.
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.