Loading vulnerability…
A heap-based buffer overflow exists in Dell OpenManage Web Server version 3.4.0. The vulnerability is triggered when a remote attacker sends an HTTP POST request containing an excessively long application variable, leading to a buffer overflow on the heap.
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 auxiliary DoS module targeting Dell OpenManage Web Server (omws32.exe) versions 3.2-3.7.1 on Windows. The exploit leverages a heap overflow vulnerability triggered by sending an overly long POST request to the /servlet/LoginServlet endpoint on TCP port 1311 (default, with SSL enabled by default). The module is designed to crash the web server, resulting in a denial of service. The code is written in Ruby and follows the standard Metasploit module structure, with the main exploit logic implemented in the 'run' method. No detection or privilege escalation is performed; the exploit is a proof-of-concept for service disruption.
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.