Example - 1

This program is intended to execute a command that lists the contents of a restricted directory, then performs other actions. Assume that it runs with setuid privileges in order to bypass the permissions check by the operating system.

// /* Raise privileges to those needed for accessing DIR. */// 
#define DIR "/restricted/directory"char cmd[500];sprintf(cmd, "ls -l %480s", DIR);RaisePrivileges(...);system(cmd);DropPrivileges(...);...

This code may look harmless at first, since both the directory and the command are set to fixed values that the attacker can't control. The attacker can only see the contents for DIR, which is the intended program behavior. Finally, the programmer is also careful to limit the code that executes with raised privileges.

However, because the program does not modify the PATH environment variable, the following attack would work:

<xhtml_ul><xhtml_li>The user sets the PATH to reference a directory under the attacker's control, such as "/my/dir/".</xhtml_li><xhtml_li>The attacker creates a malicious program called "ls", and puts that program in /my/dir</xhtml_li><xhtml_li>The user executes the program.</xhtml_li><xhtml_li>When system() is executed, the shell consults the PATH to find the ls program</xhtml_li><xhtml_li>The program finds the attacker's malicious program, "/my/dir/ls". It doesn't find "/bin/ls" because PATH does not contain "/bin/".</xhtml_li><xhtml_li>The program executes the attacker's malicious program with the raised privileges.</xhtml_li></xhtml_ul>

Example - 2

This code prints all of the running processes belonging to the current user.

// //assume getCurrentUser() returns a username that is guaranteed to be alphanumeric (avoiding CWE-78)// 
$userName = getCurrentUser();$command = 'ps aux | grep ' . $userName;system($command);

If invoked by an unauthorized web user, it is providing a web page of potentially sensitive information on the underlying system, such as command-line arguments (CWE-497). This program is also potentially vulnerable to a PATH based attack (CWE-426), as an attacker may be able to create malicious versions of the ps or grep commands. While the program does not explicitly raise privileges to run the system commands, the PHP interpreter may by default be running with higher privileges than users.

Example - 3

The following code is from a web application that allows users access to an interface through which they can update their password on the system. In this environment, user passwords can be managed using the Network Information System (NIS), which is commonly used on UNIX systems. When performing NIS updates, part of the process for updating passwords is to run a make command in the /var/yp directory. Performing NIS updates requires extra privileges.

...System.Runtime.getRuntime().exec("make");...

The problem here is that the program does not specify an absolute path for make and does not clean its environment prior to executing the call to Runtime.exec(). If an attacker can modify the $PATH variable to point to a malicious binary called make and cause the program to be executed in their environment, then the malicious binary will be loaded instead of the one intended. Because of the nature of the application, it runs with the privileges necessary to perform system operations, which means the attacker's make will now be run with these privileges, possibly giving the attacker complete control of the system.