CVE-2010-2333 json
LiteSpeed Technologies LiteSpeed Web Server 4.0.x before 4.0.15 allows remote attackers to read the source code of scripts via an HTTP requ…
published 16y ago modified 4mo ago also EUVD-2010-2343
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 60.2%
- EPSS 60.2% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
LiteSpeed Technologies LiteSpeed Web Server 4.0.x before 4.0.15 allows remote attackers to read the source code of scripts via an HTTP request with a null byte followed by a .txt file extension.
Patch / fix
Is CVE-2010-2333 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-13850)
- Published
Exploit prediction
60.20% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit auxiliary/scanner/http/litespeed_source_disclosure LiteSpeed Source Code Disclosure/Download metasploit auxiliary, normal rank
- EDB-13850 Litespeed Technologies - Web Server Remote Poison Null Byte remote, 2010-06-13
- seclists.org http://seclists.org/fulldisclosure/2010/Jun/288 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
litespeedtech.com
/latest/litespeed-web-server-4.0.15-released.html
patch, vendor-advisory
-
exploit-db.com
/exploits/13850
exploit
-
seclists.org
/fulldisclosure/2010/Jun/288
mailing-list, exploit
-
secunia.com
/advisories/40128
third-party-advisory, vendor-advisory
-
osvdb.org
/65476
vdb-entry
- litespeedtech.com /support/forum/showthread.php?t=4078
-
securityfocus.com
/bid/40815
vdb-entry
Sources
- CVE List CVE-2010-2333
- NVD CVE-2010-2333
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.