Uncontrolled Recursion

Opis

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

Inne nazwy

Stack Exhaustion

Skutki

• Availability

  DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)

  Resources including CPU, memory, and stack memory could be rapidly consumed or exhausted, eventually leading to an exit or crash.

• Confidentiality

  Read Application Data

  In some cases, an application's interpreter might kill a process or thread that appears to be consuming too much resources, such as with PHP's memory_limit setting. When the interpreter kills the process/thread, it might report an error containing detailed information such as the application's installation path.

Zapobieganie

• Implementation

  Ensure that an end condition will be reached under all logic conditions. The end condition may include checking against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.

  Skuteczność: Moderate

• Implementation

  Increase the stack size.

  Skuteczność: Limited

Przykłady podatności

• CVE-2007-1285 Deeply nested arrays trigger stack exhaustion.
• CVE-2007-3409 Self-referencing pointers create infinite loop and resultant stack exhaustion.
• CVE-2016-10707 Javascript application accidentally changes input in a way that prevents a recursive call from detecting an exit condition.
• CVE-2016-3627 An attempt to recover a corrupted XML file infinite recursion protection counter was not always incremented missing the exit condition.
• CVE-2019-15118 USB-audio driver's descriptor code parsing allows unlimited recursion leading to stack exhaustion.

Słabość nadrzędna

• CWE-834 Excessive Iteration

Słabości podrzędne

• CWE-776 Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

Kiedy powstaje

• Implementation — The uncontrolled recursion is often due to an improper or missing conditional

Dotyczy

Not Language-Specific

Źródła

1. Automated Source Code Reliability Measure (ASCRM) — Object Management Group (OMG), ASCRM-CWE-674, 2016