This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Unrestricted Critical Resource Lock"

From OWASP
Jump to: navigation, search
m (Reverted edits by KirstenS (Talk); changed back to last version by Weilin Zhong)
Line 1: Line 1:
−
{{Template:Stub}}
+
{{Template:Vulnerability}}
−
'''Example 1:''' The following Java method never closes the file handle it opens. The finalize() method for FileInputStream eventually calls close(), but there is no guarantee as to how long it will take before the finalize() method will be invoked. In a busy environment, this can result in the JVM using up all of its file handles.
+
 
 +
==Description==
 +
 
 +
==Examples ==
  
−
<pre>
+
==Related Threats==
−
private void processFile(String fName) throws FileNotFoundException, IOException
 
−
{
 
−
  FileInputStream fis = new FileInputStream(fName);
 
−
  int sz;
 
−
  byte[] byteArray = new byte[BLOCK_SIZE];
 
−
  while ((sz = fis.read(byteArray)) != -1) {
 
−
processBytes(byteArray, sz);
 
−
  }
 
−
}
 
−
</pre>
 
  
−
'''Example 2:''' 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 will run out of available cursors and not be able to execute any more SQL queries.
+
==Related Attacks==
  
−
<pre>
+
==Related Vulnerabilities==
−
...
 
−
SqlConnection conn = new SqlConnection(connString);
 
−
SqlCommand cmd = new SqlCommand(queryString);
 
−
cmd.Connection = conn;
 
−
conn.Open();
 
−
SqlDataReader rdr = cmd.ExecuteReader();
 
−
HarvestResults(rdr);
 
−
conn.Connection.Close();
 
−
...
 
−
</pre>
 
  
−
'''Example 3:''' The following C function does not close the file handle it opens if an error occurs. If the process is long-lived, the process can run out of file handles.
+
==Related Countermeasures==
  
−
<pre>
+
==Categories==
−
int decodeFile(char* fName)
 
−
{
 
−
char buf[BUF_SZ];
 
−
FILE* f = fopen(fName, "r");
 
−
 
−
if (!f) {
 
−
printf("cannot open %s\n", fName);
 
−
return DECODE_FAIL;
 
−
} else {
 
−
while (fgets(buf, BUF_SZ, f)) {
 
−
if (!checkChecksum(buf)) {
 
−
  return DECODE_FAIL;
 
−
} else {
 
−
  decodeBlock(buf);
 
−
}
 
−
}
 
−
}
 
−
fclose(f);
 
−
return DECODE_SUCCESS;
 
−
}
 
−
</pre>
 
  
 +
{{Template:Stub}}
  
 
[[Category:Synchronization and Timing Vulnerability]]
 
[[Category:Synchronization and Timing Vulnerability]]

Revision as of 13:15, 3 October 2008

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.


Description

Examples

Related Threats

Related Attacks

Related Vulnerabilities

Related Countermeasures

Categories

This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.
Retrieved from "https://wiki.owasp.org/index.php?title=Unrestricted_Critical_Resource_Lock&oldid=41882"