Path Equivalence: '/./' (Single Dot Directory)
Incomplete Variant
Structure: Simple
Description
The product accepts path input in the form of single dot directory exploit ('/./') 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.
Common Consequences 1
Scope: ConfidentialityIntegrity
Impact: Read Files or DirectoriesModify Files or Directories
Potential Mitigations 1
Phase: Implementation
Strategy: Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (Incorrect Behavior Order: Validate Before Canonicalize). Make sure that the application does not decode the same input twice (Double Decoding of the Same Data). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Observed Examples 5
CVE-2000-0004Server allows remote attackers to read source code for executable files by inserting a . (dot) into the URL.
CVE-2002-0304Server allows remote attackers to read password-protected files via a /./ in the HTTP request.
CVE-1999-1083Possibly (could be a cleansing error)
CVE-2004-0815"/./////etc" cleansed to ".///etc" then "/etc"
CVE-2002-0112Server allows remote attackers to view password protected files via /./ in the URL.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Implementation
Functional Areas
- File Processing
Affected Resources
- File or Directory
Related Weaknesses
Taxonomy Mapping
- PLOVER
- Software Fault Patterns