Variant · Low-Medium

CWE-51: Path Equivalence: '/multiple//internal/slash'

The product accepts path input in the form of multiple internal slash ('/multiple//internal/slash/') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker t...

CWE-51 · Variant Level ·1 CVEs ·1 Mitigations

Description

The product accepts path input in the form of multiple internal slash ('/multiple//internal/slash/') 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.

Potential Impact

Confidentiality, Integrity

Read Files or Directories, Modify Files or Directories

Mitigations & Prevention

Implementation

Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.

Real-World CVE Examples

CVE IDDescription
CVE-2002-1483Read files with full pathname using multiple internal slash.

Taxonomy Mappings

  • PLOVER: — /multiple//internal/slash ('multiple internal slash')
  • Software Fault Patterns: SFP16 — Path Traversal

Frequently Asked Questions

What is CWE-51?

CWE-51 (Path Equivalence: '/multiple//internal/slash') is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Variant-level weakness. The product accepts path input in the form of multiple internal slash ('/multiple//internal/slash/') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker t...

How can CWE-51 be exploited?

Attackers can exploit CWE-51 (Path Equivalence: '/multiple//internal/slash') to read files or directories, modify files or directories. This weakness is typically introduced during the Implementation phase of software development.

How do I prevent CWE-51?

Key mitigations include: Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (C

What is the severity of CWE-51?

CWE-51 is classified as a Variant-level weakness (Low-Medium abstraction). It has been observed in 1 real-world CVEs.