Difference between revisions of "Asymmetric resource consumption (amplification)"

Jump to: navigation, search
Line 32: Line 32:
After using up all handles (file descriptors) VM may become very unstable, slow and what is the most immportant it may stop working
After using up all handles (file descriptors) the VM may become very unstable, slow, and may stop working
deterministically comparing to its previous state.
deterministically comparing to its previous state.
[[Category:FIXME|I wasn't sure what was meant by "deterministically comparing to its previous state" . Can that part of the sentence be deleted?]]

Revision as of 16:53, 5 September 2008

This is an Attack. To view all attacks, please see the Attack Category page.

ASDR Table of Contents

Last revision (mm/dd/yy): 09/5/2008


An attacker can force a victim to consume more resources than should be allowed for the attacker's level of access. The program can potentially fail to release or incorrectly release a system resource. A resource is not properly cleared and made available for re-use.

Risk Factors



The following method never closes the file handle it opens. The Finalize() method for StreamReader eventually calls Close(), but there is no guarantee how long it is going to take before the Finalize() method is invoked. In fact, there is no guarantee that Finalize() will ever be invoked. In a busy environment, this can result in the VM using up all of its available file handles.

private void processFile(string fName) {
 StreamWriter sw = new
 string line;
 while ((line = sr.ReadLine()) != null) processLine(line);

After using up all handles (file descriptors) the VM may become very unstable, slow, and may stop working deterministically comparing to its previous state.


Under normal conditions the following C# code executes a database query, processes the results returned by the database, and closes the allocated SqlConnection object. But if an exception occurs while executing the SQL or processing the results, the SqlConnection object is not closed. If this happens often enough, the database runs out of available cursors and is not able to execute any more SQL queries.

C# Example:

SqlConnection conn = new SqlConnection(connString);
SqlCommand cmd = new SqlCommand(queryString);
cmd.Connection = conn; conn.Open();
SqlDataReader rdr = cmd.ExecuteReader();

The amount of the concurent connections to the databases is often lower than maximal amount of possible handles in the system to use. It makes easier to locate application bottlenecks and use them to stop the application or make it unstable.


If application which can handle N concurent connections doesn't implement appropriate mechanism to disconnect clients e.g. TIMEOUTs, then it's very easy to disable it by establishing close to N connections. Additionally the connections should simulate work with application using its protocol untill exhaustion of the available resources.

Related Threat Agents

Related Attacks

Related Vulnerabilities

Related Controls

It is good practice to be responsible for freeing all resources you allocate.

Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].