導入モード
Implementation
適用可能なプラットフォーム
言語
クラス: Not Language-Specific (Undetermined)
一般的な結果
| スコープ |
影響 |
可能性 |
| Other | Reduce Reliability
注記:When an exception handling block (such as a Catch and Finally block) is used, but that block is empty, this can prevent the product from running reliably. If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability. | |
潜在的な緩和策
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/
登録情報
| 名前 |
組織 |
日付 |
リリース日 |
Version |
| CWE Content Team |
MITRE |
2018-07-02 +00:00 |
2019-01-03 +00:00 |
3.2 |
変更履歴
| 名前 |
組織 |
日付 |
コメント |
| CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated Relationships, Type |
| CWE Content Team |
MITRE |
2022-10-13 +00:00 |
updated Applicable_Platforms, Demonstrative_Examples, Potential_Mitigations |
| CWE Content Team |
MITRE |
2023-01-31 +00:00 |
updated Description |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated 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, Mapping_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Common_Consequences, Description, Time_of_Introduction |
| CWE Content Team |
MITRE |
2026-04-30 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Demonstrative_Examples, Detection_Factors |