CVE-2005-3293 json
Xerver 4.17 allows remote attackers to (1) obtain source code of scripts via a request with a trailing "." (dot) or (2) list directory cont…
published 2005-10-23 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3292
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.8%
- EPSS 7.8% chance of exploitation in 30 days, percentile 94%
- public exploits
- 2
- Exploit-DB
Summary
Xerver 4.17 allows remote attackers to (1) obtain source code of scripts via a request with a trailing "." (dot) or (2) list directory contents via a trailing null character.
Patch / fix
- securityfocus.com/bid/15135 patch
- secunia.com/advisories/17243 advisory
Timeline
- First public exploit (EDB-26375)
- Published
Exploit prediction
7.82% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-26375 Xerver 4.17 - Forced Directory Listing remote, 2005-10-19
- EDB-26374 Xerver 4.17 - Single Dot File Request Source Disclosure remote, 2005-10-19
- securityfocus.com http://www.securityfocus.com/bid/15135 referenced PoC, tagged "exploit" by a source, unverified
- secunia.com http://secunia.com/advisories/17243 referenced PoC, tagged "exploit" by a source, unverified
- securitytracker.com http://securitytracker.com/id?1015079 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 |
References
-
securityfocus.com
/bid/15135
vdb-entry, exploit, patch
-
secunia.com
/advisories/17243
third-party-advisory, exploit, patch, vendor-advisory
-
securitytracker.com
/id?1015079
vdb-entry, exploit
-
osvdb.org
/20076
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/22785
vdb-entry
-
osvdb.org
/20075
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/22786
vdb-entry
Sources
- CVE List CVE-2005-3293
- NVD CVE-2005-3293
Fencer Vulns 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.