CVE-2005-3293
published 2005-10-23CVE-2005-3293: 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…
PriorityP425medium5CVSS 2.0
AVNACLAuNCPINAN
EXPLOIT
EPSS
3.49%
87.7th percentile
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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| xerver | xerver | — | — |
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
Exploit-DB
Xerver 4.17 - Forced Directory Listing
exploitdb·2005-10-19
CVE-2005-3293 Xerver 4.17 - Forced Directory Listing
Xerver 4.17 - Forced Directory Listing
---
source: https://www.securityfocus.com/bid/15135/info
Xerver is prone to multiple input validation vulnerabilities. These issues are due to a failure in the application to properly sanitize user-supplied input.
An attacker can exploit a vulnerability to disclose the contents of any Web accessible script. Information obtained may aid in further attacks.
An attacker can retrieve a directory listing of any Web accessible folders. Information obtained may aid in further attacks.
An attacker can perform cross-site scripting attacks. This may be leveraged to have arbitrary script code executed in the browser of an unsuspecting user in the context of the affected site. This may facilitate the theft of cookie-based authentication credentials as well
Exploit-DB
Xerver 4.17 - Single Dot File Request Source Disclosure
exploitdb·2005-10-19
CVE-2005-3293 Xerver 4.17 - Single Dot File Request Source Disclosure
Xerver 4.17 - Single Dot File Request Source Disclosure
---
source: https://www.securityfocus.com/bid/15135/info
Xerver is prone to multiple input validation vulnerabilities. These issues are due to a failure in the application to properly sanitize user-supplied input.
An attacker can exploit a vulnerability to disclose the contents of any Web accessible script. Information obtained may aid in further attacks.
An attacker can retrieve a directory listing of any Web accessible folders. Information obtained may aid in further attacks.
An attacker can perform cross-site scripting attacks. This may be leveraged to have arbitrary script code executed in the browser of an unsuspecting user in the context of the affected site. This may facilitate the theft of cookie-based authentication cre
No writeups or analysis indexed.
CWE
Path Equivalence: 'filename.' (Trailing Dot)
mitre_cwe·CVSS 5.0
CVE-2000-1114 [MEDIUM] CWE-42 Path Equivalence: 'filename.' (Trailing Dot)
CWE-42: Path Equivalence: 'filename.' (Trailing Dot)
The product accepts path input in the form of trailing dot ('filedir.') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Access Control. Impact: Bypass Protection Mechanism.
Observed Examples:
CVE-2000-1114: Source code disclosure using trailing dot
CVE-2002-1986: Source code disclosure using trailing dot
CVE-2004-2213: Source code disclosure using trailing dot
CVE-2005-3293: Source code disclosure using trailing dot
CVE-2004-0061: Bypass directory access restrictions using trailing dot in URL
CVE-2000-1133: Bypass directory access rest
CWE
Improper Resolution of Path Equivalence
mitre_cwe
CWE-41 Improper Resolution of Path Equivalence
CWE-41: Improper Resolution of Path Equivalence
The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object.
Path equivalence is usually employed in order to circumvent access controls expressed using an incomplete set of file name or file path representations. This is different from path traversal, wherein the manipulations are performed to generate a name for a different object.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Confidentiality, Integrity, Access Control. Impact: Read Files or Directories, Modify Files or Directories, Bypass Protection Mechanism. A
CWE
Improper Neutralization of Null Byte or NUL Character
mitre_cwe
CWE-158 Improper Neutralization of Null Byte or NUL Character
CWE-158: Improper Neutralization of Null Byte or NUL Character
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes NUL characters or null bytes when they are sent to a downstream component.
As data is parsed, an injected NUL character or null byte may cause the product to believe the input is terminated earlier than it actually is, or otherwise cause the input to be misinterpreted. This could then be used to inject potentially dangerous input that occurs after the null byte or otherwise bypass validation routines and other protection mechanisms.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Integrity. Impact: Unexpected State.
Potential Mitigations:
Developers should anticipate that null characters or
http://secunia.com/advisories/17243http://securitytracker.com/id?1015079http://www.osvdb.org/20075http://www.osvdb.org/20076http://www.securityfocus.com/bid/15135https://exchange.xforce.ibmcloud.com/vulnerabilities/22785https://exchange.xforce.ibmcloud.com/vulnerabilities/22786http://secunia.com/advisories/17243http://securitytracker.com/id?1015079http://www.osvdb.org/20075http://www.osvdb.org/20076http://www.securityfocus.com/bid/15135https://exchange.xforce.ibmcloud.com/vulnerabilities/22785https://exchange.xforce.ibmcloud.com/vulnerabilities/22786
2005-10-23
Published