Loading vulnerability…
A stack-based buffer overflow exists in the OmniInet process of HP OpenView Data Protector Application Recovery Manager versions 5.50 and 6.0. The vulnerability is triggered by sending a specially crafted MSG_PROTOCOL packet to the service, which can result in the execution of arbitrary code or a denial of service condition.
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 (1 hidden).
This repository contains a single Metasploit exploit module targeting a stack-based buffer overflow vulnerability (CVE-2009-3844) in the HP OmniInet NT Service, which is installed with HP OpenView Data Protector and HP Application Recovery Manager on Windows systems. The exploit works by sending a specially crafted MSG_PROTOCOL (0x010b) packet to the service's default TCP port 5555, triggering a buffer overflow via a vulnerable wcscpy() call. The module supports automatic target detection and includes hardcoded return addresses for several specific product versions. The payload is customizable and allows for arbitrary code execution with elevated privileges. The module also includes a check method to detect vulnerable targets. The only network endpoint involved is TCP port 5555, which is the default for the vulnerable service. The code is written in Ruby and is designed to be used within the Metasploit framework.
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.