CWE-431 詳細資料

A handler is not available or implemented.

When an exception is thrown and not caught, the process has given up an opportunity to decide if a given failure or event is worth a change in execution.

引入方式

Implementation

適用平台

程式語言

類別： Not Language-Specific (Undetermined)

常見後果

觀察到的案例

潛在緩解措施

Phases : Implementation
Handle all possible situations (e.g. error condition).
Phases : Implementation
If an operation can throw an Exception, implement a handler for that specific exception.

偵測方法

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.)

漏洞對應備注

理由說明 : This CWE entry is at the Base 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-62

The Art of Software Security Assessment
Mark Dowd, John McDonald, Justin Schuh.

提交

修改記錄