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
Weilin Zhong (talk | contribs) |
(Reverting to last version not containing links to www.textricrodro.com) |
||
| (12 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{template:CandidateForDeletion}} |
| − | + | #REDIRECT [[Failure to follow guideline/specification]] | |
| − | |||
| − | + | ||
| + | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| + | |||
==Description== | ==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. | 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 == | ==Examples == | ||
| Line 22: | Line 28: | ||
thr.run(); | thr.run(); | ||
| − | [[ | + | ==Related [[Attacks]]== |
| + | |||
| + | * [[Attack 1]] | ||
| + | * [[Attack 2]] | ||
| + | |||
| + | |||
| + | ==Related [[Vulnerabilities]]== | ||
| + | |||
| + | * [[Vulnerability 1]] | ||
| + | * [[Vulnerabiltiy 2]] | ||
| + | |||
| + | |||
| + | ==Related [[Controls]]== | ||
| + | |||
| + | * [[Control 1]] | ||
| + | * [[Control 2]] | ||
| + | |||
| + | |||
| + | ==Related [[Technical Impacts]]== | ||
| − | [[ | + | * [[Technical Impact 1]] |
| + | * [[Technical Impact 2]] | ||
| − | |||
| − | [[ | + | ==References== |
| + | Note: A reference to related [http://cwe.mitre.org/ CWE] or [http://capec.mitre.org/ CAPEC] article should be added when exists. Eg: | ||
| − | [[ | + | * [http://cwe.mitre.org/data/definitions/79.html CWE 79]. |
| + | * http://www.link1.com | ||
| + | * [http://www.link2.com Title for the link2] | ||
Latest revision as of 18:30, 27 May 2009
#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:
