Strategy: Input Validation 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.
No detection method information available for this CWE.
No examples or observed CVEs available for this CWE.
CWE-52: CWE-52: Path Equivalence: '/multiple/trailing/slash//' is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Description
If exploited, CWE-52 (CWE-52: Path Equivalence: '/multiple/trailing/slash//') it can compromise Read Files or Directories and Modify Files or Directories, leading to outcomes such as Scope: Confidentiality and Integrity.
Recommended mitigations for CWE-52 include: Strategy: Input Validation 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.
CWE-52 commonly affects Languages. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
A CWE (Common Weakness Enumeration) like CWE-52 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.