Understanding Insecure Deserialisation
cybersecuritydeserialisationvulnerabilitiesexploitationmitigation
Insecure deserialization is a critical vulnerability that occurs when applications process serialized data without proper validation. Attackers can manipulate this data to execute arbitrary code, bypass authentication, or cause system crashes. This vulnerability consistently ranks in the OWASP Top 10 due to its severe potential impact.
Key Points
- Serialization converts objects into storable formats (JSON, XML, binary) for transmission or persistence
- Deserialization reconstructs objects from serialized data—if tampered, malicious code can execute
- Attackers exploit this by injecting crafted payloads through cookies, API requests, or file uploads
- Common impacts include remote code execution (RCE), privilege escalation, and denial-of-service
- Mitigation requires using safe formats like JSON, validating all input, and restricting deserialization to trusted classes
How the Attack Works
Attack Flow
- Injection: Attacker crafts malicious serialized data and injects it via user input, cookies, or API requests
- Processing: Application deserializes the data without validation or integrity checks
- Execution: Malicious payload triggers, potentially executing arbitrary code or manipulating application logic
Common Attack Vectors
- Session data: Serialized session objects stored in client-side cookies
- API payloads: Untrusted JSON/XML data in POST/PUT requests
- File uploads: Malicious files disguised as legitimate serialized data
- Message queues: Tampered serialized objects in inter-process communication
Real-World Examples
| Vulnerability | CVE ID | Impact | Mitigation |
|---|---|---|---|
| Log4j RCE | CVE-2021-44228 | Arbitrary code execution via JNDI lookups in serialized data | Disable JNDI lookups; update to patched version |
| WebLogic RCE | CVE-2015-4852 | Remote command execution through Java deserialization | Apply security patches; implement class whitelisting |
| Jenkins Flaw | CVE-2016-0792 | RCE via crafted serialized objects in HTTP requests | Update Jenkins; restrict deserialization input |
Detection Techniques
White-Box Testing (With Source Code)
Focus on vulnerable functions:
- PHP:
unserialize() - Java:
ObjectInputStream,readObject() - Python:
pickle.loads(),yaml.load() - .NET:
BinaryFormatter
Example vulnerable code:
// VULNERABLE: User input directly deserialized
$data = $_GET['user_data'];
$object = unserialize($data);
Black-Box Testing (Without Source Code)
Detection methods:
- Analyze error messages for deserialization-related exceptions
- Look for base64-encoded or binary data in cookies and headers
- Test for serialized object patterns (e.g.,
O:in PHP,rO0in Java) - Fuzz serialized payloads using Burp Suite or OWASP ZAP
- Monitor server responses for timing anomalies
Mitigation Strategies
For Developers
Use safe data formats:
- Replace native serialization with JSON or XML whenever possible
- Avoid
pickle(Python),unserialize()(PHP), and Java's native serialization
Implement input validation:
# SAFE: JSON deserialization with validation
import json
try:
data = json.loads(user_input)
# Validate expected structure
if not isinstance(data, dict) or 'expected_key' not in data:
raise ValueError("Invalid data structure")
except (json.JSONDecodeError, ValueError) as e:
# Handle error safely
log_error(e)
Apply integrity checks:
- Use digital signatures (HMAC) to verify data hasn't been tampered with
- Implement class whitelisting for Java using
ObjectInputFilter - Set strict type checking before processing deserialized objects
Secure coding practices:
// SAFE: Java deserialization with filtering
ObjectInputFilter filter = ObjectInputFilter.Config.createFilter(
"com.example.SafeClass;!*"
);
ois.setObjectInputFilter(filter);
For Security Teams
Static analysis:
- Scan codebases for dangerous deserialization functions
- Review all instances where user input flows to deserialization
- Check for missing integrity verification
Dynamic testing:
- Fuzz applications with malformed serialized payloads
- Test boundary conditions and unexpected data types
- Use tools like ysoserial (Java) and PHPGGC (PHP) for payload generation
Runtime protections:
- Deploy Web Application Firewalls (WAFs) with deserialization rules
- Monitor logs for unusual deserialization errors or patterns
- Implement rate limiting on endpoints accepting serialized data
Security Checklist
- Replace native serialization with JSON/XML where feasible
- Validate and sanitize all serialized data before processing
- Implement digital signatures to verify data integrity
- Use class whitelisting for deserialization (Java's
ObjectInputFilter) - Never deserialize data from untrusted sources without validation
- Log and monitor all deserialization attempts for anomalies
- Keep serialization libraries and frameworks updated
- Conduct regular security audits of deserialization code paths
Learn More
OWASP Resources:
Standards and References:
Security Tools:
- ysoserial - Java deserialization payload generator
- PHPGGC - PHP deserialization gadget chains
- Burp Suite - Web application security testing