A subprocess with an argument list and shell=False avoids passing user text through a command shell. Validate options and executable paths separately.
What You Will Learn
This lesson focuses on Preventing Command Injection with subprocess. You will connect the operation to a concrete input, inspect the result and identify the situation in which a different approach would be safer or clearer.
Security-sensitive operations are correct only when they remain safe under invalid, unexpected and attacker-controlled inputs. A normal-case example alone does not establish that safety.
How It Works
Decide which inputs are trusted, which privileges are needed, how secrets are managed, and how the result is validated. Security primitives solve specific problems; using the wrong primitive can create a false sense of protection.
Worked Example
The following example isolates the main behavior so you can run it from a local Python installation. Read the inputs first, then follow the operation and the final printed result.
import subprocess, sys
completed = subprocess.run([sys.executable, "-c", "print(2 + 3)"], capture_output=True, text=True, check=True, timeout=5)
print(completed.stdout.strip())Understanding the Example
Start with the setup and import statements; these define the objects that the operation needs. Follow each assignment or function call in order, noting which arguments are provided and whether the operation creates a new value, changes existing state or returns a result. Finally, inspect the printed value or assertion rather than assuming that the operation worked.
The important behavior demonstrated here is: A subprocess with an argument list and shell=False avoids passing user text through a command shell. Validate options and executable paths separately. The example uses deliberately small values so the intermediate result is easy to reason about. A larger application must still handle validation, errors and resource cleanup.
Environment note: this example may require a separately installed package, local service, platform permission or network connection. Set up the indicated environment before running it; it has not been executed automatically for this guide.
When to Use This Approach
Use small local demonstrations to learn each primitive, and adopt current security parameters and reviews before handling real secrets or sensitive data.
Important Behavior and Edge Cases
Concatenating an untrusted filename into shell=True and relying on ad hoc quote replacement.
Prefer proven libraries and narrow APIs over custom cryptography, string-based command construction or broad exception suppression. Do not print credentials, generated tokens or confidential payloads in logs.
Practice Exercise
Rewrite a shell command to use an explicit argument list and an allowed executable.
Before running your modified code, predict the output or expected failure. Confirm the result using at least one ordinary case and one invalid, missing or boundary input. If the operation accesses external resources, first exercise it against a controlled local or test environment.
Common Beginner Mistakes
- Concatenating an untrusted filename into shell=True and relying on ad hoc quote replacement.
- Prefer proven libraries and narrow APIs over custom cryptography, string-based command construction or broad exception suppression. Do not print credentials, generated tokens or confidential payloads in logs.
Key Takeaways
- A subprocess with an argument list and shell=False avoids passing user text through a command shell. Validate options and executable paths separately.
- Choose this technique for the problem it solves, but validate inputs and follow the cleanup and failure behavior shown above.
- Next practice step: Rewrite a shell command to use an explicit argument list and an allowed executable.