A stack-based buffer overflow exists in the ovalarm.exe component of HP OpenView Network Node Manager (OV NNM) versions 7.01, 7.51, and 7.53. The vulnerability is triggered by sending a specially crafted HTTP request with an excessively long Accept-Language header to the OVABverbose action, resulting in a buffer overflow on the stack.
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 module targeting a stack buffer overflow vulnerability in HP OpenView Network Node Manager 7.53, specifically in the ovalarm.exe CGI component. The exploit works by sending a specially crafted HTTP GET request to the '/OvCgi/ovalarm.exe' endpoint, with an 'Accept-Language' header exceeding 100 bytes and the 'OVABverbose' URI variable set to '1'. This triggers a buffer overflow in the isWide function, allowing arbitrary code execution. The module supports custom Metasploit payloads (such as reverse shells), which are injected via the overflowed header. The exploit is operational and has been tested with a reverse_ord_tcp payload. The code is written in Ruby and is structured as a standard Metasploit exploit module, making use of the Metasploit framework's HTTP client and payload handling capabilities. The only fingerprintable endpoint is the '/OvCgi/ovalarm.exe' CGI path, which must be accessible on the target system for exploitation.
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.