이름: Uncaught Exception in Servlet

The Servlet does not catch all exceptions.

일반 정보

취약점 도입 방식

Implementation

적용 가능한 플랫폼

언어

이름: Java (Undetermined)

기술

이름: Web Server (Undetermined)

일반적인 결과

범위	영향	가능성
Confidentiality Availability	Read Application Data, DoS: Crash, Exit, or Restart 참고: When a Servlet throws an exception, the default error response the Servlet container sends back to the user typically includes debugging information. This information is of great value to an attacker. For example, a stack trace might show the attacker a malformed SQL query string, the type of database being used, and the version of the application container. This information enables the attacker to target known vulnerabilities in these components.

잠재적 완화 방법

Phases : Implementation
Implement Exception blocks to handle all types of Exceptions.

취약점 매핑 메모

근거 : 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.

메모

The "Missing Catch Block" concept is probably broader than just Servlets, but the broader concept is not sufficiently covered in CWE.

제출

이름	조직	날짜	출시일	Version
CWE Community		2006-12-15 +00:00	2006-12-15 +00:00	Draft 5

수정 사항

이름	조직	날짜	댓글
Eric Dalci	Cigital	2008-07-01 +00:00	updated Potential_Mitigations, Time_of_Introduction
CWE Content Team	MITRE	2008-09-08 +00:00	updated Relationships, Other_Notes
CWE Content Team	MITRE	2009-03-10 +00:00	updated Alternate_Terms, Description, Maintenance_Notes, Name, Other_Notes, Relationships
CWE Content Team	MITRE	2009-05-27 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2010-12-13 +00:00	updated Description, Name
CWE Content Team	MITRE	2011-03-29 +00:00	updated Relationships
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 Demonstrative_Examples, Relationships
CWE Content Team	MITRE	2012-10-30 +00:00	updated 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 Taxonomy_Mappings
CWE Content Team	MITRE	2021-03-15 +00:00	updated Demonstrative_Examples
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	2025-12-11 +00:00	updated Applicable_Platforms, Weakness_Ordinalities
CWE Content Team	MITRE	2026-10-28 +00:00	updated Common_Consequences, Description

CWE-600 상세 정보

CWE-600