ClassIncomplete

CWE-834Excessive Iteration

Category: other

Description

The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed. If 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 product or its host system; it depends on the amount of resources consumed per iteration.

Common consequences· 1

  • Availability — DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Amplification, DoS: Crash, Exit, or Restart
    Excessive looping will cause unexpected consumption of resources, such as CPU cycles or memory. The product'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.

References

  1. https://cwe.mitre.org/data/definitions/834.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Excessive Platform Resource Consumption within a Loop
CWE
Uncontrolled Recursion
CWE
Loop with Unreachable Exit Condition ('Infinite Loop')
CWE
Unchecked Input for Loop Condition
CWE
Memory Allocation with Excessive Size Value
CWE
Integer Overflow to Buffer Overflow
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.