CWE-1069 상세 정보

An invokable code block contains an exception handling block that does not contain any code, i.e. is empty.

취약점 도입 방식

Implementation

적용 가능한 플랫폼

언어

클래스: Not Language-Specific (Undetermined)

일반적인 결과

잠재적 완화 방법

Phases : Implementation
For every exception block add code that handles the specific exception in the way intended by the application.

탐지 방법

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. In many cases, the use of an empty exception block may only indicate a quality issue. However, in some cases, it prevents the product from appropriately responding to security-critical events. Consider also mapping to the higher-level weakness that is resultant from this one. Note: this weakness was formerly 'Prohibited' for mapping from CWE 4.14 (2024-02-29) to CWE 4.19.1 (2026-01-21).

참고 자료

REF-961

Automated Source Code Reliability Measure (ASCRM)
Object Management Group (OMG).
http://www.omg.org/spec/ASCRM/1.0/

제출

수정 사항