A stack-based buffer overflow vulnerability exists in magentservice.exe, a component of the server in HP LoadRunner 11.00 prior to patch 4. The vulnerability is triggered by a crafted size value in a network packet, which allows remote attackers to overflow a stack buffer and execute arbitrary code. The issue was initially misattributed to HP Diagnostics Server, but HP clarified that the affected product is HP LoadRunner.
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 (hp_magentservice.rb) that exploits a stack buffer overflow vulnerability in HP Diagnostics Server magentservice.exe (version 9.10) on Windows. The exploit targets the service over TCP port 23472 (default), sending a specially crafted packet that overflows a buffer and overwrites the SEH handler, allowing for arbitrary code execution. The module supports customizable Metasploit payloads (up to 1000 bytes, avoiding null bytes) and is operational, providing remote code execution if successful. The code is written in Ruby and follows standard Metasploit module structure, including references to CVE-2011-4789 and other advisories. No hardcoded IP addresses or URLs are present, but the TCP port 23472 is fingerprintable as the service endpoint.
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.