CWE-41: Improper Resolution of Path Equivalence

BaseIncomplete

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.

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Frequently Asked Questions

What is CWE-41: Improper Resolution of Path Equivalence?+

CWE-41: Improper Resolution of Path Equivalence is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Improper Resolution of Path Equivalence?+

If exploited, CWE-41 (Improper Resolution of Path Equivalence) it can compromise Confidentiality, Integrity and Access Control, leading to outcomes such as Read Files or Directories, Modify Files or Directories and Bypass Protection Mechanism.

How is Improper Resolution of Path Equivalence detected?+

CWE-41 can be detected using Manual Static Analysis - Source Code and Architecture or Design Review. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Improper Resolution of Path Equivalence?+

CWE-41 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 Improper Resolution of Path Equivalence?+

MITRE documents real CVEs mapped to CWE-41, including CVE-2000-1114, CVE-2002-1986, CVE-2004-2213, CVE-2005-3293 and CVE-2004-0061. 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-41 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.

Learn More

CWE-41: Improper Resolution of Path Equivalence | CWE Lookup | InventiveHQ