CWE-585
Weakness AllowedEmpty Synchronized Block
Abstraction: Variant · Status: Draft
The product contains an empty synchronized block.
Mapping guidance
This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Modes of introduction
An empty synchronized block can occur because code no longer needed within the synchronized block is commented out without removing the synchronized block.
Detection methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Effectiveness: High
Content history
Submitted by members of the CWE community to extend early CWE versions
updated Potential_Mitigations, Time_of_Introduction
updated Relationships, Other_Notes
updated Common_Consequences, Demonstrative_Examples, Description, Other_Notes, Potential_Mitigations, References
updated Common_Consequences
updated Relationships
updated Relationships, Taxonomy_Mappings
updated Relationships
updated Relationships, Weakness_Ordinalities
updated Relationships, Type
updated Description
updated Detection_Factors, References, Relationships, Type
updated Mapping_Notes
updated Demonstrative_Examples
updated Demonstrative_Examples
updated Common_Consequences, Description, Modes_of_Introduction
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
Mitigation
When you come across an empty synchronized statement, or a synchronized statement in which the code has been commented out, try to determine what the original intentions were and whether or not the synchronized block is still necessary.
No CAPEC attack patterns related to this CWE.