Manipulate variables that reference files with "dot-dot-slash (../)" to access restricted directories in the application.

Manipulate variables that reference files with "dot-dot-slash (../)" to access restricted directories in the application.

• A. Canonicalization
• B. Path Traversal
• C. URL Redirection
• D. Buffer Overflow

Answer: (A)

Path traversal vulnerabilities occur when an application uses user-supplied input to build file paths without proper validation, allowing an attacker to ascend directories and access restricted files. By injecting dot-dot-slash sequences, the attacker can escape the intended folder and reach sensitive parts of the filesystem, potentially reading config files, logs, or other restricted data. The risk arises because the path is constructed from untrusted input and then used to access or include files without ensuring the final path stays within a permitted base directory. Defenses include canonicalizing and validating the path, resolving it to an absolute form, and enforcing that the resulting path remains under a designated base directory. Avoid directly concatenating user input into file paths, and implement checks that the resolved path begins with the allowed base path. Canonicalization is related as a technique to normalize paths and help prevent traversal, while the attack itself is about abusing path references to reach restricted locations. This isn’t about URL redirection or a buffer overflow.

Path traversal vulnerabilities occur when an application uses user-supplied input to build file paths without proper validation, allowing an attacker to ascend directories and access restricted files. By injecting dot-dot-slash sequences, the attacker can escape the intended folder and reach sensitive parts of the filesystem, potentially reading config files, logs, or other restricted data. The risk arises because the path is constructed from untrusted input and then used to access or include files without ensuring the final path stays within a permitted base directory. Defenses include canonicalizing and validating the path, resolving it to an absolute form, and enforcing that the resulting path remains under a designated base directory. Avoid directly concatenating user input into file paths, and implement checks that the resolved path begins with the allowed base path. Canonicalization is related as a technique to normalize paths and help prevent traversal, while the attack itself is about abusing path references to reach restricted locations. This isn’t about URL redirection or a buffer overflow.