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
| Line 1: | Line 1: | ||
| − | {{ | + | {{template:CandidateForDeletion}} |
| − | + | ||
| + | #REDIRECT [[Failure to follow guideline/specification]] | ||
| + | |||
__TOC__ | __TOC__ | ||
| Line 8: | Line 10: | ||
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| − | |||
| − | |||
| − | |||
| Line 56: | Line 55: | ||
TBD | TBD | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 16:25, 17 February 2009
#REDIRECT Failure to follow guideline/specification
Last revision (mm/dd/yy): 02/17/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
