Insufficient Resource Pool

Opis

The product's resource pool is not large enough to handle peak demand, which allows an attacker to prevent others from accessing the resource by using a (relatively) large number of requests for resources.

Frequently the consequence is a "flood" of connection or sessions.

Skutki

• Availability, Integrity, Other

  DoS: Crash, Exit, or Restart; Other

  Floods often cause a crash or other problem besides denial of the resource itself; these are likely examples of *other* vulnerabilities, not an insufficient resource pool.

Zapobieganie

• Architecture and Design

  Do not perform resource-intensive transactions for unauthenticated users and/or invalid requests.

• Architecture and Design

  Consider implementing a velocity check mechanism which would detect abusive behavior.

• Operation

  Consider load balancing as an option to handle heavy loads.

• Implementation

  Make sure that resource handles are properly closed when no longer needed.

• Architecture and Design

  Identify the system's resource intensive operations and consider protecting them from abuse (e.g. malicious automated script which runs the resources out).

Przykłady podatności

• CVE-1999-1363 Large number of locks on file exhausts the pool and causes crash.
• CVE-2001-1340 Product supports only one connection and does not disconnect a user who does not provide credentials.
• CVE-2002-0406 Large number of connections without providing credentials allows connection exhaustion.

Słabość nadrzędna

• CWE-664 Improper Control of a Resource Through its Lifetime

Może prowadzić do

• CWE-400 Uncontrolled Resource Consumption

Kiedy powstaje

• Architecture and Design
• Implementation
• Operation

Dotyczy

Not Language-Specific

Źródła

1. Writing Secure Code — Michael Howard, David LeBlanc, Chapter 17, "Protecting Against Denial of Service Attacks" Page 517, Microsoft Press, 2002