CWE-22 - Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Weakness Name: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Description: The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Many file operations are intended to take place within a restricted directory. By using special elements such as ".." and "/" separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the "../" sequence, which in most modern operating systems is interpreted as the parent directory of the current location. This is referred to as relative path traversal. Path traversal also covers the use of absolute pathnames such as "/usr/local/bin" to access unexpected files. This is referred to as absolute path traversal.

Common Consequences: Scope: Integrity, Confidentiality, Availability
Impact: Execute Unauthorized Code or Commands
Notes: The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Scope: Integrity
Impact: Modify Files or Directories
Notes: The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Scope: Confidentiality
Impact: Read Files or Directories
Notes: The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Scope: Availability
Impact: DoS: Crash, Exit, or Restart
Notes: The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.

CWE-22 High