Home > CAPEC List > CAPEC-125: Flooding (Version 2.11)  

CAPEC-125: Flooding

 
Flooding
Definition in a New Window Definition in a New Window
Attack Pattern ID: 125
Abstraction: Meta
Status: Stable
Completeness: Complete
Presentation Filter:
+ 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.

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

+ Typical Severity

Medium

+ Typical Likelihood of Exploit

Likelihood: High

+ Resources Required

A script or program capable of generating more requests than the target can handle, or a network or cluster of objects all capable of making simultaneous requests.

+ Solutions and 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.

+ Attack Motivation-Consequences
ScopeTechnical ImpactNote
Availability
DoS: instability
DoS: resource consumption (CPU)
DoS: resource consumption (memory)
A successful flooding attack compromises the availability of the target system's service by exhausting its available resources.
+ Content History
Submissions
SubmitterOrganizationDateSource
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team
Modifications
ModifierOrganizationDateCommentsSource
CAPEC Content TeamThe MITRE Corporation2017-05-01Updated Activation_Zone, Attack_Motivation-Consequences, Description Summary, Injection_Vector, Payload, Payload_Activation_Impact, Solutions_and_Mitigations, Typical_Likelihood_of_ExploitInternal

More information is available — Please select a different filter.
Page Last Updated or Reviewed: July 31, 2017