CVE-2001-1193
published 2001-12-13CVE-2001-1193: Directory traversal vulnerability in EFTP 2.0.8.346 allows local users to read directories via a ... (modified dot dot) in the CWD command.
PriorityP416medium5CVSS 2.0
AVNACLAuNCPINAN
EPSS
2.26%
80.8th percentile
Directory traversal vulnerability in EFTP 2.0.8.346 allows local users to read directories via a ... (modified dot dot) in the CWD command.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| khamil_landross_and_zack_jones | eftp | — | — |
Stop checking back — get the weekly exploitation signal.
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.
No public exploits indexed.
No writeups or analysis indexed.
CWE
Path Traversal: '...' (Triple Dot)
mitre_cwe
CWE-32 Path Traversal: '...' (Triple Dot)
CWE-32: Path Traversal: '...' (Triple Dot)
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '...' (triple dot) sequences that can resolve to a location that is outside of that directory.
This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory. The '...' manipulation is useful for bypassing some path traversal protection schemes. On some Windows systems, it is equivalent to "..\.." and might bypass checks that assume only two dots are valid. Incomplete filtering, such as removal of "./" sequences, can ultimately produce valid ".." sequences due to a collapse into unsafe value (CWE-182).
Modes of Introduction:
Phase: Implementation
CWE
Relative Path Traversal
mitre_cwe
CWE-23 Relative Path Traversal
CWE-23: Relative Path Traversal
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Integrity, Confidentiality, Availability. Impact: Execute Unauthorized Code or Commands. The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Scope: Integrity. Impact: Modify Files or Directories. The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able
http://www.eftp.org/releasehistory.htmlhttp://www.kb.cert.org/vuls/id/413875http://www.osvdb.org/2003http://www.securityfocus.com/archive/1/245393http://www.securityfocus.com/bid/3691https://exchange.xforce.ibmcloud.com/vulnerabilities/7699http://www.eftp.org/releasehistory.htmlhttp://www.kb.cert.org/vuls/id/413875http://www.osvdb.org/2003http://www.securityfocus.com/archive/1/245393http://www.securityfocus.com/bid/3691https://exchange.xforce.ibmcloud.com/vulnerabilities/7699
2001-12-13
Published