Asymmetric Resource Consumption (Amplification)

Opis

The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."

This can lead to poor performance due to "amplification" of resource consumption, typically in a non-linear fashion. This situation is worsened if the product allows malicious users or attackers to consume more resources than their access level permits.

Skutki

• Availability

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

  Sometimes this is a factor in "flood" attacks, but other types of amplification exist.

Zapobieganie

• Architecture and Design

  An application must make resources available to a client commensurate with the client's access level.

• Architecture and Design

  An application must, at all times, keep track of allocated resources and meter their usage appropriately.

• System Configuration

  Consider disabling resource-intensive algorithms on the server side, such as Diffie-Hellman key exchange.

  Skuteczność: High

Przykłady podatności

• CVE-1999-0513 Classic "Smurf" attack, using spoofed ICMP packets to broadcast addresses.
• CVE-2003-1564 Parsing library allows XML bomb
• CVE-2004-2458 Tool creates directories before authenticating user.
• CVE-2020-10735 Python has "quadratic complexity" issue when converting string to int with many digits in unexpected bases
• CVE-2020-5243 server allows ReDOS with crafted User-Agent strings, due to overlapping capture groups that cause excessive backtracking.
• CVE-2013-5211 composite: NTP feature generates large responses (high amplification factor) with spoofed UDP source addresses.
• CVE-2002-20001 Diffie-Hellman (DHE) Key Agreement Protocol allows attackers to send arbitrary numbers that are not public keys, which causes the server to perform expensive, unnecessary computation of modular exponentiation.
• CVE-2022-40735 The Diffie-Hellman Key Agreement Protocol allows use of long exponents, which are more computationally expensive than using certain "short exponents" with particular properties.

Słabość nadrzędna

• CWE-400 Uncontrolled Resource Consumption

Słabości podrzędne

• CWE-406 Insufficient Control of Network Message Volume (Network Amplification)
• CWE-407 Inefficient Algorithmic Complexity
• CWE-408 Incorrect Behavior Order: Early Amplification
• CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
• CWE-776 Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
• CWE-1050 Excessive Platform Resource Consumption within a Loop
• CWE-1072 Data Resource Access without Use of Connection Pooling
• CWE-1073 Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses
• CWE-1084 Invokable Control Element with Excessive File or Data Access Operations
• CWE-1089 Large Data Table with Excessive Number of Indices
• CWE-1094 Excessive Index Range Scan for a Data Resource
• CWE-1176 Inefficient CPU Computation

Kiedy powstaje

• Architecture and Design
• Implementation
• Operation

Dotyczy

Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Not Technology-Specific, Client Server

Źródła

1. Catastrophic backtracking — Ilya Kantor, 2020