CVE-2025-34108 is a stack-based buffer overflow in the login functionality of Disk Pulse Enterprise version 9.0.34. The flaw is triggered by sending a specially crafted HTTP POST request to the /login endpoint with an overly long username parameter. The vulnerable condition is reported to occur in the libspp.dll component, where insufficient bounds checking on the username input leads to a stack buffer overflow. Successful exploitation can result in arbitrary 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 targeting a stack buffer overflow vulnerability in Disk Pulse Enterprise 9.0.34 (CVE-2025-34108). The exploit works by sending a specially crafted HTTP POST request to the '/login' endpoint, overflowing a buffer and executing arbitrary code as NT AUTHORITY\SYSTEM. The module uses the egghunter technique to locate the payload in memory, which is tagged with 'w00tw00t'. The exploit is operational and allows for customizable payloads via Metasploit, typically resulting in a shell or Meterpreter session. The module also includes a check method to verify the target version by sending a GET request to '/'. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.