In this lesson, you will learn why using the pickle module on untrusted data is a severe security risk and how to avoid arbitrary code execution attacks.
The Danger of pickle
When you use pickle.load() or pickle.loads(), Python does more than just read data; it reconstructs entire Python objects. This process can be tricked into executing arbitrary code.
The pickle protocol allows an object to define a special method called __reduce__. When pickle encounters this method during deserialization, it executes the instructions found there. If an attacker provides a malicious "pickled" file, they can include instructions that command your computer to delete files, steal data, or open a network connection—all under the permissions of your script.
A Hypothetical Attack
Imagine you are building a system that saves user profiles as binary files using pickle. If an attacker replaces a legitimate user profile with a malicious pickle string, your code might look like this:
import pickle
# A malicious attacker creates a file that, when loaded, runs:
# import os; os.system('rm -rf /')
with open('user_profile.pkl', 'rb') as f:
# THIS IS DANGEROUS!
# The moment this executes, the system command runs.
data = pickle.load(f)
Because pickle is powerful enough to instantiate arbitrary Python objects, it is fundamentally insecure when handling data from sources you don't control, such as user uploads or network requests.
How to Mitigate the Risk
The most effective way to secure your application is to never unpickle data received from untrusted sources. Instead, use safer serialization formats for data exchange.
- Prefer
json: As you learned previously,jsonis a text-based format that only supports simple data types like strings, numbers, lists, and dictionaries. Because it cannot represent complex Python objects, it cannot execute arbitrary code during deserialization. - Use Digital Signatures: If you absolutely must use
pickle(for example, to store data internally on a secure, restricted server), use a cryptographic signature (likehmac) to verify that the data was created by your own application and hasn't been tampered with.
Key Takeaway: Never deserialize data with pickle from a source you cannot guarantee is 100% trustworthy, as it allows attackers to execute arbitrary code on your system.