Rule Definition
The software constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. This could allow attackers to execute unexpected, dangerous commands directly on the operating system. This weakness can lead to a vulnerability in environments in which the attacker does not have direct access to the operating system, such as in web applications. OS command injection (second order) - The application stores data in a database. At a later time, the data is subsequently read back into the application and included in an OS command without sanitization.

Remediation
Assume all input is malicious. Avoid using inputs. If it is not possible, use an "accept known good" input validation strategy, i.e., use stringent white-lists that limit the character set based on the expected value of the parameter in the request. This will indirectly limit the scope of an attack.

Violation Code Sample

...
resultSet = preparedStatement.executeQuery();
script = resultSet.getString(1);
...
System.exec(script);

Fixed Code Sample

...
resultSet = preparedStatement.executeQuery();
script = resultSet.getString(1);
//code a validate function for the input recieved "script"
...
System.exec(script);

CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') https://cwe.mitre.org/data/definitions/78.html Open Web Application Security Project (OWASP) https://www.owasp.org/index.php/Top_10_2007 CISQ rule: ASCSM-CWE-078.