CAPEC Definitions

    CAPEC Definitions / CAPEC-231

    CAPEC-231: Oversized Serialized Data Payloads

    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.

    Severity:High
    Possibility:Medium

    Extended Description

    Applications often need to transform data in and out of serialized data formats, such as XML and YAML, by using a data parser. It may be possible for an adversary to inject data that may have an adverse effect on the parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the parser, an adversary can cause the parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An adversary's goal is to leverage parser failure to their advantage. DoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious data payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.

    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.

    Relationships with other CAPECs

    CAPEC-130: Excessive Allocation

    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.

    Related Weaknesses

    CWE-112: Missing XML Validation

    CWE-20: Improper Input Validation

    CWE-674: Uncontrolled Recursion

    CWE-770: Allocation of Resources Without Limits or Throttling