이름: J2EE Bad Practices: Use of System.exit()

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)

일반적인 결과

범위	영향	가능성
Availability	DoS: Crash, Exit, or Restart 참고: Access to a function that can shut down the application is an avenue for Denial of Service (DoS) attacks, since use of System.exit() also shuts down the application's container.

잠재적 완화 방법

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

제출

이름	조직	날짜	출시일	Version
7 Pernicious Kingdoms		2006-07-19 +00:00	2006-07-19 +00:00	Draft 3

수정 사항

이름	조직	날짜	댓글
Sean Eidemiller	Cigital	2008-07-01 +00:00	added/updated demonstrative examples
Eric Dalci	Cigital	2008-07-01 +00:00	updated Time_of_Introduction
CWE Content Team	MITRE	2008-09-08 +00:00	updated Relationships, Other_Notes, Taxonomy_Mappings
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences, Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2012-05-11 +00:00	updated Relationships
CWE Content Team	MITRE	2014-06-23 +00:00	updated Description, Modes_of_Introduction, Other_Notes, Potential_Mitigations
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2017-11-08 +00:00	updated Relationships
CWE Content Team	MITRE	2019-01-03 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2020-02-24 +00:00	updated References, Relationships
CWE Content Team	MITRE	2023-04-27 +00:00	updated Detection_Factors, Relationships
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2024-02-29 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2025-12-11 +00:00	updated Applicable_Platforms, Relationships, Weakness_Ordinalities
CWE Content Team	MITRE	2026-10-28 +00:00	updated Common_Consequences, Description, Dimensions, Potential_Mitigations, References

CWE-382 상세 정보

CWE-382