CAPECattack pattern

CAPEC-528 XML Flood

Medium Official page ↗
Abstraction
Standard
Status
Draft
Likelihood of attack
Low
Typical severity
Medium
CAPEC version
3.9

Description

An adversary may execute a flooding attack using XML messages with the intent to deny legitimate users access to a web service. These attacks are accomplished by sending a large number of XML based requests and letting the service attempt to parse each one. In many cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing.

Extended description

XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. 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.

Execution flow

1. [Explore] [Survey the target] Using a browser or an automated tool, an attacker records all instance of web services to process XML requests. 2. [Experiment] An adversary crafts input data that may have an adverse effect on the operation of the web service when the XML data sent to the service. 3. [Exploit] [Launch a resource depletion attack] The attacker delivers a large number of XML messages to the target URLs found in the explore phase at a sufficiently rapid rate. It causes denial of service to the target application.

Prerequisites

• The target must receive and process XML transactions. • An adverssary must possess the ability to generate a large amount of XML based messages to send to the target service.

Skills required

• [Low] Denial of service

Consequences

• Availability: Resource Consumption

Mitigations

• Design: Build throttling mechanism into the resource allocation. Provide for a timeout mechanism for allocated resources whose transaction does not complete within a specified interval. • Implementation: Provide for network flow control and traffic shaping to control access to the resources.

Related

Att&ck technique · MITRE ATT&CK (2)

  • T1498.001 Direct Network Flood sub-technique
  • T1499.002 Service Exhaustion Flood sub-technique

Child of · CAPEC (1)

Weakness · CWE (1)

  • CWE-770 Allocation of Resources Without Limits or Throttling weakness

Referenced by CAPEC · child of (1)

  • CAPEC-147 XML Ping of the Death attack pattern

Referenced by CWE · attack pattern (1)

  • CWE-770 Allocation of Resources Without Limits or Throttling weakness