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 "Poor Style: Empty Synchronized Block"
From OWASP
Weilin Zhong (talk | contribs) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{template:CandidateForDeletion}} |
| − | {{ | + | |
| + | #REDIRECT [[Failure to follow guideline/specification]] | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| − | |||
| − | |||
==Description== | ==Description== | ||
| + | |||
| + | This synchronized block contains no statements; it is unlikely the synchronization achieves the intended effect. | ||
Synchronization in Java can be tricky. An empty synchronized block is often a sign that a programmer is wrestling with synchronization but has not yet achieved the result they intend. | Synchronization in Java can be tricky. An empty synchronized block is often a sign that a programmer is wrestling with synchronization but has not yet achieved the result they intend. | ||
| − | ==Examples == | + | |
| + | ==Risk Factors== | ||
| + | |||
| + | TBD | ||
| + | |||
| + | ==Examples== | ||
<pre> | <pre> | ||
| Line 16: | Line 27: | ||
</pre> | </pre> | ||
| − | ==Related | + | ==Related [[Attacks]]== |
| + | |||
| + | * [[Attack 1]] | ||
| + | * [[Attack 2]] | ||
| + | |||
| + | |||
| + | ==Related [[Vulnerabilities]]== | ||
| + | |||
| + | * [[Vulnerability 1]] | ||
| + | * [[Vulnerabiltiy 2]] | ||
| − | ==Related | + | ==Related [[Controls]]== |
| − | + | * [[Control 1]] | |
| + | * [[Control 2]] | ||
| − | |||
| − | == | + | ==Related [[Technical Impacts]]== |
| − | [[ | + | * [[Technical Impact 1]] |
| + | * [[Technical Impact 2]] | ||
| − | |||
| − | + | ==References== | |
| − | + | TBD | |
Latest revision as of 23:29, 7 April 2009
#REDIRECT Failure to follow guideline/specification
Last revision (mm/dd/yy): 04/7/2009
Description
This synchronized block contains no statements; it is unlikely the synchronization achieves the intended effect.
Synchronization in Java can be tricky. An empty synchronized block is often a sign that a programmer is wrestling with synchronization but has not yet achieved the result they intend.
Risk Factors
TBD
Examples
synchronized(this) { }
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
TBD
