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 "Code Correctness: Call to Thread.run()"

From OWASP
Jump to: navigation, search
(Reverting to last version not containing links to www.textricrodro.com)
 
Line 1: Line 1:
http://www.textricrodro.com
 
 
{{template:CandidateForDeletion}}
 
{{template:CandidateForDeletion}}
  

Latest revision as of 18:30, 27 May 2009

Template:CandidateForDeletion

#REDIRECT Failure to follow guideline/specification


Last revision (mm/dd/yy): 05/27/2009


Description

The program calls a thread's run() method instead of calling start().

In most cases a direct call to a Thread object's run() method is a bug. The programmer intended to begin a new thread of control, but accidentally called run() instead of start(), so the run() method will execute in the caller's thread of control.

Risk Factors

TBD

Examples

The following excerpt from a Java program mistakenly calls run() instead of start().

   Thread thr = new Thread() {
     public void run() {
       ...
     } 
   };
   thr.run();

Related Attacks


Related Vulnerabilities


Related Controls


Related Technical Impacts


References

Note: A reference to related CWE or CAPEC article should be added when exists. Eg: