CAPEC-125 Flooding

CAPEC ID: 125

CAPEC-125 Metadata

Likelihood of Attack

High

Typical Severity

Medium

Overview

Summary

An adversary consumes the resources of a target by rapidly engaging in a large number of interactions with the target. This type of attack generally exposes a weakness in rate limiting or flow. When successful this attack prevents legitimate users from accessing the service and can cause the target to crash. This attack differs from resource depletion through leaks or allocations in that the latter attacks do not rely on the volume of requests made to the target but instead focus on manipulation of the target's operations. The key factor in a flooding attack is the number of requests the adversary can make in a given period of time. The greater this number, the more likely an attack is to succeed against a given target.

Prerequisites

Any target that services requests is vulnerable to this attack on some level of scale.

Potential Solutions / Mitigations

Ensure that protocols have specific limits of scale configured. Specify expectations for capabilities and dictate which behaviors are acceptable when resource allocation reaches limits. Uniformly throttle all requests in order to make it more difficult to consume resources more quickly than they can again be freed.

Related Weaknesses (CWE)

CWE ID Description
CWE-404 Improper Resource Shutdown or Release
CWE-770 Allocation of Resources Without Limits or Throttling

Taxonomy Mappings

Taxonomy: ATTACK

Entry ID Entry Name
1498.001 Network Denial of Service: Direct Network Flood
1499 Endpoint Denial of Service

Taxonomy: WASC

Entry ID Entry Name
10 Denial of Service

Taxonomy: OWASP Attacks

Entry ID Entry Name
Link Traffic flood

Stay Ahead of Attack Patterns

Understanding CAPEC patterns helps security professionals anticipate and thwart potential attacks. Leverage these insights to enhance threat modeling, strengthen your software development lifecycle, and train your security teams effectively.