Description
The software uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize ‘….’ (multiple dot) sequences that can resolve to a location that is outside of that directory.
Modes of Introduction:
– Implementation
Related Weaknesses
Consequences
Confidentiality, Integrity: Read Files or Directories, Modify Files or Directories
Potential Mitigations
Phase: Implementation
Effectiveness: High
Description:
Phase: Implementation
Description:
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.
CVE References
- CVE-2000-0240
- read files via “/………./” in URL
- CVE-2000-0773
- read files via “….” in web server
- CVE-1999-1082
- read files via “……” in web server (doubled triple dot?)
- CVE-2004-2121
- read files via “……” in web server (doubled triple dot?)
- CVE-2001-0491
- multiple attacks using “..”, “…”, and “….” in different commands
- CVE-2001-0615
- “…” or “….” in chat server