CAPEC-231
Oversized Serialized Data Payloads
MEDIUM
HIGH
Draft
2014-06-23 00:00 +00:00
2022-09-29 00:00 +00:00
Alerte pour un CAPEC
Stay informed of any changes for a specific CAPEC.
Description
An adversary injects oversized serialized data payloads into a parser during data processing to produce adverse effects upon the parser such as exhausting system resources and arbitrary code execution.
Informations
Execution Flow
1) Explore
An adversary determines the input data stream that is being processed by an serialized data parser on the victim's side.
2) Experiment
An adversary crafts input data that may have an adverse effect on the operation of the data parser when the data is parsed on the victim's system.
Prerequisites
An application uses an parser for serialized data to perform transformation on user-controllable data.An application does not perform sufficient validation to ensure that user-controllable data is safe for a data parser.
Skills Required
Denial of serviceArbitrary code execution
Mitigations
Carefully validate and sanitize all user-controllable serialized data prior to passing it to the parser routine. Ensure that the resultant data is safe to pass to the parser.Perform validation on canonical data.
Pick a robust implementation of the serialized data parser.
Validate data against a valid schema or DTD prior to parsing.
Related Weaknesses
| Weakness Name | |
|---|---|
| Missing XML Validation The product accepts XML from an untrusted source but does not validate the XML against the proper schema. |
|
| Improper Input Validation The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
|
| Uncontrolled Recursion The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack. |
|
| Allocation of Resources Without Limits or Throttling The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. |
References
REF-89
XML Parser Attacks: A summary of ways to attack an XML ParserShlomo, Yona.
http://yeda.cs.technion.ac.il/~yona/talks/xml_parser_attacks/slides/slide2.html
Submission
| Name | Organization | Date | Date Release |
|---|---|---|---|
| CAPEC Content Team | The MITRE Corporation |
Modifications
| Name | Organization | Date | Comment |
|---|---|---|---|
| CAPEC Content Team | The MITRE Corporation | Updated Alternate_Terms, Description, Execution_Flow, Related_Attack_Patterns | |
| CAPEC Content Team | The MITRE Corporation | Updated @Name, Description, Execution_Flow, Indicators, Mitigations, Prerequisites | |
| CAPEC Content Team | The MITRE Corporation | Updated Description, Notes | |
| CAPEC Content Team | The MITRE Corporation | Updated Related_Weaknesses | |
| CAPEC Content Team | The MITRE Corporation | Updated Description, Extended_Description |
2024©
tesweb SA
