Nama: Empty Synchronized Block

The product contains an empty synchronized block.

Informasi Umum

Mode Pengenalan

Implementation : An empty synchronized block can occur because code no longer needed within the synchronized block is commented out without removing the synchronized block.

Platform yang Berlaku

Bahasa

Nama: Java (Undetermined)

Konsekuensi Umum

Cakupan	Dampak	Kemungkinan
Other	Other Catatan: An empty synchronized block does not actually accomplish any synchronization and may indicate a troubled section of code. An empty synchronized block will wait until nobody else is using the synchronizer being specified. While this may be part of the desired behavior, because you haven't protected the subsequent code by placing it inside the synchronized block, nothing is stopping somebody else from modifying whatever it was you were waiting for while you run the subsequent code.

Mitigasi yang Memungkinkan

Phases : Implementation
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.

Metode Deteksi

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.)
Efektivitas : High

Catatan Pemetaan Kerentanan

Justifikasi : 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.
Komentar : 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.

Referensi

REF-478

Intrinsic Locks and Synchronization (in Java)
https://docs.oracle.com/javase/tutorial/essential/concurrency/locksync.html

Pengajuan

Nama	Organisasi	Tanggal	Tanggal rilis	Version
CWE Community		2006-12-15 +00:00	2006-12-15 +00:00	Draft 5

Modifikasi

Nama	Organisasi	Tanggal	Komentar
Eric Dalci	Cigital	2008-07-01 +00:00	updated Potential_Mitigations, Time_of_Introduction
CWE Content Team	MITRE	2008-09-08 +00:00	updated Relationships, Other_Notes
CWE Content Team	MITRE	2009-05-27 +00:00	updated Common_Consequences, Demonstrative_Examples, Description, Other_Notes, Potential_Mitigations, References
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2012-05-11 +00:00	updated Relationships
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2017-11-08 +00:00	updated Relationships
CWE Content Team	MITRE	2019-01-03 +00:00	updated Relationships, Weakness_Ordinalities
CWE Content Team	MITRE	2020-02-24 +00:00	updated Relationships, Type
CWE Content Team	MITRE	2023-01-31 +00:00	updated Description
CWE Content Team	MITRE	2023-04-27 +00:00	updated Detection_Factors, References, Relationships, Type
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2024-02-29 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2025-04-03 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2026-10-28 +00:00	updated Common_Consequences, Description, Modes_of_Introduction

Detail CWE-585

CWE-585