Loading vulnerability…
hagent.exe in Wyse Device Manager (WDM) 4.7.x fails to enforce authentication for management commands. This allows remote attackers to send crafted queries, such as a V52 query, to the agent and execute management actions like powering off the device without any authentication.
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 exploit module targeting the Wyse Rapport Hagent service (CVE-2009-0695). The exploit works by impersonating a legitimate update server: it starts both an HTTP and FTP server on the attacker's machine, then contacts the target's Hagent service to indicate an update is available. The target is tricked into downloading a malicious payload (EXE for Windows or binary for Linux) from the attacker's FTP server and executing it, resulting in remote code execution. The module supports both Windows XPe and Wyse Linux x86 targets. The exploit is fully weaponized, leveraging Metasploit's payload generation and handler capabilities. The main attack vector is network-based, requiring the attacker to be able to communicate with the target's Hagent service and run services on standard ports. The code also references a potential registry modification on Windows, though this is commented out. The structure is typical for a Metasploit module, with clear separation of initialization, 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.