CAPECattack pattern
CAPEC-229 Serialized Data Parameter Blowup
High
Official page ↗
- Abstraction
- Detailed
- Status
- Draft
- Likelihood of attack
- High
- Typical severity
- High
- CAPEC version
- 3.9
Description
This attack exploits certain serialized data parsers (e.g., XML, YAML, etc.) which manage data in an inefficient manner. The attacker crafts an serialized data file with multiple configuration parameters in the same dataset. In a vulnerable parser, this results in a denial of service condition where CPU resources are exhausted because of the parsing algorithm. The weakness being exploited is tied to parser implementation and not language specific.
Execution flow
1. [Explore] [Survey the target] Using a browser or an automated tool, an attacker records all instances of web services to process requests using serialized data.
2. [Exploit] [Launch a Blowup attack] The attacker crafts malicious messages that contain multiple configuration parameters in the same dataset.
Prerequisites
• The server accepts input in the form of serialized data and is using a parser with a runtime longer than O(n) for the insertion of a new configuration parameter in the data container.(examples are .NET framework 1.0 and 1.1)
Mitigations
• This attack may be mitigated completely by using a parser that is not using a vulnerable container.
• Mitigation may limit the number of configuration parameters per dataset.
Related
Child of · CAPEC (1)
- CAPEC-231 Oversized Serialized Data Payloads attack pattern
Weakness · CWE (1)
- CWE-770 Allocation of Resources Without Limits or Throttling weakness
Referenced by CWE · attack pattern (1)
- CWE-770 Allocation of Resources Without Limits or Throttling weakness