CAPEC-79: Using Slashes in Alternate Encoding
This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Weaknesses
# ID | Name | Type |
---|---|---|
CWE-20 | Improper Input Validation | weakness |
CWE-22 | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | weakness |
CWE-73 | External Control of File Name or Path | weakness |
CWE-74 | Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') | weakness |
CWE-173 | Improper Handling of Alternate Encoding | weakness |
CWE-180 | Incorrect Behavior Order: Validate Before Canonicalize | weakness |
CWE-181 | Incorrect Behavior Order: Validate Before Filter | weakness |
CWE-185 | Incorrect Regular Expression | weakness |
CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor | weakness |
CWE-697 | Incorrect Comparison | weakness |
CWE-707 | Improper Neutralization | weakness |