| Home > CAPEC List > CAPEC-229: Serialized Data Parameter Blowup (Version 3.9) |
|
High
High
| Nature | Type | ID | Name |
|---|---|---|---|
| ChildOf | Standard Attack PatternStandard Attack Pattern - A standard level attack pattern in CAPEC is focused on a specific methodology or technique used in an attack. It is often seen as a singular piece of a fully executed attack. A standard attack pattern is meant to provide sufficient details to understand the specific technique and how it attempts to accomplish a desired goal. A standard level attack pattern is a specific type of a more abstract meta level attack pattern. | 231 | Oversized Serialized Data Payloads |
| View Name | Top Level Categories |
|---|---|
| Domains of Attack | Software |
| Mechanisms of Attack | Abuse Existing Functionality |
Survey the target: Using a browser or an automated tool, an attacker records all instances of web services to process requests using serialized data.
| Techniques |
|---|
| Use an automated tool to record all instances of URLs to process requests from serialized data. |
| Use a browser to manually explore the website and analyze how the application processes requests using serialized data. |
Launch a Blowup attack: The attacker crafts malicious messages that contain multiple configuration parameters in the same dataset.
| Techniques |
|---|
| Send the malicious crafted message containing the multiple configuration parameters to the target URL, causing a denial of service. |
In this example, assume that the victim is running a vulnerable parser such as .NET framework 1.0. This results in a quadratic runtime of O(n^2).
A document with n attributes results in (n^2)/2 operations to be performed. If an operation takes 100 nanoseconds then a document with 100,000 operations would take 500s to process. In this fashion a small message of less than 1MB causes a denial of service condition on the CPU resources.
A YAML bomb leverages references within a YAML file to create exponential growth in memory requirements. By creating a chain of keys whose values are a list of multiple references to the next key in the chain, the amount of memory and processing required to handle the data grows exponentially. This may lead to denial of service or instability resulting from excessive resource consumption.
| CWE-ID | Weakness Name |
|---|---|
| 770 | Allocation of Resources Without Limits or Throttling |
| Entry ID | Entry Name |
|---|---|
| 41 | XML Attribute Blowup |
| Submissions | |||
|---|---|---|---|
| Submission Date | Submitter | Organization | |
| 2014年06月23日 (Version 2.6) | CAPEC Content Team | The MITRE Corporation | |
| Modifications | |||
| Modification Date | Modifier | Organization | |
| 2017年08月04日 (Version 2.11) | CAPEC Content Team | The MITRE Corporation | |
| Updated Activation_Zone, Attack_Phases, Description, Description Summary, Examples-Instances, Injection_Vector, Methods_of_Attack, Payload, Related_Attack_Patterns, Typical_Likelihood_of_Exploit, Typical_Severity | |||
| 2020年07月30日 (Version 3.3) | CAPEC Content Team | The MITRE Corporation | |
| Updated @Name, Description, Example_Instances, Execution_Flow, Mitigations, Prerequisites | |||
| 2020年12月17日 (Version 3.4) | CAPEC Content Team | The MITRE Corporation | |
| Updated Taxonomy_Mappings | |||
| 2022年09月29日 (Version 3.8) | CAPEC Content Team | The MITRE Corporation | |
| Updated Example_Instances | |||
| Previous Entry Names | |||
| Change Date | Previous Entry Name | ||
| 2020年07月30日 (Version 3.3) | XML Attribute Blowup | ||
|
Use of the Common Attack Pattern Enumeration and Classification (CAPEC), and the associated references from this website are subject to the Terms of Use. Copyright © 2007–2025, The MITRE Corporation. CAPEC and the CAPEC logo are trademarks of The MITRE Corporation. |
||