Excessive IterationID: 834 | Date: (C)2012-05-14 (M)2022-10-10 |
Type: weakness | Status: INCOMPLETE |
Abstraction Type: Base |
Description
The software performs an iteration or loop without sufficiently
limiting the number of times that the loop is executed.
Extended DescriptionIf the iteration can be influenced by an attacker, this weakness could
allow attackers to consume excessive resources such as CPU or memory. In
many cases, a loop does not need to be infinite in order to cause enough
resource consumption to adversely affect the software or its host system; it
depends on the amount of resources consumed per iteration.
Applicable PlatformsNone
Common Consequences
Scope | Technical Impact | Notes |
---|
Availability | DoS: resource consumption
(CPU)DoS: resource consumption
(memory)DoS: amplificationDoS: crash / exit /
restart | Excessive looping will cause unexpected consumption of resources,
such as CPU cycles or memory. The software's operation may slow down, or
cause a long time to respond. If limited resources such as memory are
consumed for each iteration, the loop may eventually cause a crash or
program exit due to exhaustion of resources, such as an out-of-memory
error. |
Detection MethodsNone
Potential MitigationsNone
Relationships
Related CWE | Type | View | Chain |
---|
CWE-834 ChildOf CWE-691 | Weakness | CWE-1000CWE-699 | |
Demonstrative ExamplesNone
White Box Definitions None
Black Box Definitions None
Taxynomy MappingsNone
References:
- Mark Dowd John McDonald Justin Schuh .The Art of Software Security Assessment 1st Edition. Addison Wesley. Section:'Chapter 7, "Looping Constructs", Page
327.'. Published on 2006.