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()"
| Line 40: | Line 40: | ||
* [[Vulnerability 1]] | * [[Vulnerability 1]] | ||
* [[Vulnerabiltiy 2]] | * [[Vulnerabiltiy 2]] | ||
| − | |||
| − | |||
| Line 48: | Line 46: | ||
* [[Control 1]] | * [[Control 1]] | ||
* [[Control 2]] | * [[Control 2]] | ||
| − | |||
| − | |||
Revision as of 20:17, 22 September 2008
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
- This article includes content generously donated to OWASP by
Last revision (mm/dd/yy): 09/22/2008
Vulnerabilities Table of Contents
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:
