An unspecified vulnerability in HP LoadRunner versions prior to 11.52 allows remote attackers to execute arbitrary code via unknown vectors. The vulnerability is referenced as ZDI-CAN-1671 and is one of several critical issues affecting HP LoadRunner that enable remote code execution.
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_loadrunner_writefilebinary.rb) that exploits a remote code execution vulnerability (CVE-2013-2370) in the lrFileIOService ActiveX control installed with HP LoadRunner 11.50. The exploit targets Internet Explorer versions 6 through 9 on Windows XP, Vista, and 7. It works by serving a malicious HTML page containing JavaScript that performs a heap spray and instantiates the vulnerable ActiveX control, triggering the WriteFileBinary method with attacker-controlled data. This allows arbitrary code execution in the context of the browser user. The module supports multiple targets and uses ROP chains to bypass ASLR where necessary. The payload is fully customizable via Metasploit, making this a weaponized, operational exploit. The only fingerprintable endpoints are the HTTP server delivering the exploit and the specific ActiveX classid targeted.
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.