Loading vulnerability…
Pi3Web 2.0.3 before PL2, when installed on Windows as a desktop application and not using the Pi3Web/Conf/Intenet.pi3 configuration, is vulnerable to a denial of service and information disclosure. Remote attackers can send a request to a non-DLL file within the ISAPI directory (e.g., Isapi\users.txt), causing the server to crash or hang due to a failed DLL load. This also results in the disclosure of the full server pathname in the error output.
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 auxiliary module targeting a denial of service (DoS) vulnerability in the Pi3Web HTTP server (CVE-2008-6938). The exploit works by sending an HTTP request for a non-DLL file (such as users.txt) in the /isapi directory, which causes the server to crash on versions 2.0.13 and earlier. The module is written in Ruby and leverages Metasploit's Remote::HttpClient and Auxiliary::Dos mixins. The only configurable option is the filename to request in the /isapi directory. There are no payloads or post-exploitation features; the sole purpose is to crash the target service. The attack vector is network-based, requiring access to the HTTP service on the target. The endpoint of interest is the /isapi/<FILENAME> path, which is used to trigger the vulnerability.
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.