Starting a process with a shell detected BAN-B605
Starting a process with a shell: Seems safe, but may be changed in the future, consider rewriting without shell
84 return 0, 0, [], 0
85
86 finally:
87 os.system("taskkill /im chromedriver.exe /F")88
89
90if __name__ == "__main__":Starting a process with a shell: Seems safe, but may be changed in the future, consider rewriting without shell
67 return 0, 0, [], 0
68
69 finally:
70 os.system("taskkill /im chromedriver.exe /F")71
72
73if __name__ == "__main__":Starting a process with a shell, possible injection detected, security issue.
149):
150 task_list = []
151 terminal_size = get_terminal_size(platform)
152 os.system("clear" if os.name == "posix" else "cls")153 print(banner)
154 with ThreadPoolExecutor() as pool:
155 for kwargs in file_info:
Description
Spawning of a subprocess using a command shell is dangerous as it is vulnerable to various shell injection attacks. Great care should be taken to sanitize all input in order to mitigate this risk. Calls of this type are identified by the use of certain commands which are known to use shells.
It is possible for an attacker to craft inputs to issue different commands than the ones you intended such as removing a file.
It is recommended to use functions that don't spawn a shell. If you must use them, use shlex.quote to sanitize the input by changing it to the shell-escaped version.
Bad practice
import os
# Malicious input
filename = "file.py; echo foo"
# Executing command in a shell without escaping. This will also run `echo foo`.
os.system("git add " + filename)
Recommended
import os, shlex
# Malicious input
filename = "file.py; echo foo"
# This ensures someone can't inject other commands into the given command.
os.system("git add " + shlex.quote(filename))
References:
- Command Injection
- shlex
- OWASP Top 10 2021 Category A03 - Injection
- SANS Top 25
- CWE-78