CWE-382 詳細資料

A J2EE application uses System.exit().

引入方式

Implementation : A call to System.exit() is probably part of leftover debug code or code imported from a non-J2EE application.

適用平台

程式語言

名稱： Java (Undetermined)

技術

類別： Web Based (Undetermined)
名稱： Web Server (Undetermined)

常見後果

潛在緩解措施

Phases : Architecture and Design
The shutdown function should be a privileged function available only to a properly authorized administrative user.
Phases : Implementation
Web applications should not call methods that cause the virtual machine to exit, such as System.exit().
Phases : Implementation
Web applications should not throw any Throwables to the application server, as this may adversely affect the container.
Phases : Implementation
Non-web applications may have a main() method that contains a System.exit(), but generally should not call System.exit() from other locations in the code.

偵測方法

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-6

Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors
Katrina Tsipenyuk, Brian Chess, Gary McGraw.
https://cwe.mitre.org/documents/sources/SevenPerniciousKingdoms.pdf

提交

修改記錄