LiteSpeed Web Server 4.0.x before 4.0.15 contains a vulnerability that allows remote attackers to read the source code of server-side scripts. This is achieved by sending an HTTP request with a null byte (%00) followed by a .txt file extension, which bypasses the server's script execution and causes the script to be served as plain text.
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 (2 hidden).
This repository contains a single Metasploit auxiliary module (modules/auxiliary/scanner/http/litespeed_source_disclosure.rb) that exploits a source code disclosure vulnerability (CVE-2010-2333) in LiteSpeed Web Server versions 4.0.14 and prior. The module sends a specially crafted HTTP GET request to the target server, appending a null byte and .txt extension to the requested file path, which causes the server to return the source code of the file instead of executing it. The exploit requires the user to specify the URI of the file to download and a local path to save the file. If successful, the module saves the downloaded source code locally. The code is written in Ruby and is designed to be run within the Metasploit framework. No hardcoded IPs or domains are present; the target is specified by the user at runtime.
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.