CWE-55: Path Equivalence: '/./' (Single Dot Directory)
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.
View on MITRETechnical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Mitigation Strategies
No mitigation information available for this CWE.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
Observed CVE Examples (5)
Server allows remote attackers to read source code for executable files by inserting a . (dot) into the URL.
View DetailsServer allows remote attackers to read password-protected files via a /./ in the HTTP request.
View DetailsServer allows remote attackers to view password protected files via /./ in the URL.
View DetailsCWE Relationships
Frequently Asked Questions
What is CWE-55: Path Equivalence: '/./' (Single Dot Directory)?+
CWE-55: Path Equivalence: '/./' (Single Dot Directory) is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.
What are the security consequences of Path Equivalence: '/./' (Single Dot Directory)?+
If exploited, CWE-55 (Path Equivalence: '/./' (Single Dot Directory)) it can compromise Confidentiality and Integrity, leading to outcomes such as Read Files or Directories and Modify Files or Directories.
Which programming languages are affected by Path Equivalence: '/./' (Single Dot Directory)?+
CWE-55 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
What are real-world examples of Path Equivalence: '/./' (Single Dot Directory)?+
MITRE documents real CVEs mapped to CWE-55, including CVE-2000-0004, CVE-2002-0304, CVE-1999-1083, CVE-2004-0815 and CVE-2002-0112. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
What is the difference between a CWE and a CVE?+
A CWE (Common Weakness Enumeration) like CWE-55 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.