CWE-585 상세 정보

The product contains an empty synchronized block.

취약점 도입 방식

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

적용 가능한 플랫폼

언어

이름: Java (Undetermined)

일반적인 결과

잠재적 완화 방법

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.

탐지 방법

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.)
효과성 : High

취약점 매핑 메모

근거 : 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.

참고 자료

REF-478

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

제출

수정 사항