CVE-2013-4798 is an unspecified vulnerability in HP LoadRunner versions prior to 11.52 that allows remote attackers to execute arbitrary code via unknown vectors. The vulnerability is referenced as ZDI-CAN-1705 and is one of several critical issues affecting HP LoadRunner in this release cycle. The specific vulnerable function or component is not disclosed in public advisories.
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 targeting a remote code execution vulnerability (CVE-2013-4798) in the HP LoadRunner lrFileIOService ActiveX control (version 11.50) on Windows XP. The exploit is delivered via a malicious HTML page served by the attacker's HTTP server. When a vulnerable Internet Explorer (6.0-8.0) browser visits the page, JavaScript is used to write a malicious DLL (LrWeb2MdrvLoader.dll) to disk using the WriteFileString method of the vulnerable ActiveX control. The DLL is then loaded via the lrMdrvService control's Init() method, resulting in arbitrary code execution. The module is operational and provides a customizable payload (DLL) generated by Metasploit. The exploit is only effective on Windows XP due to later Windows versions' virtualization protections. The repository is structured as a single Ruby file, following standard Metasploit module conventions, and does not contain any extraneous files.
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.