CWE-594 상세 정보

The J2EE container attempts to write unserializable objects to disk.

In heavy load conditions, most J2EE application frameworks flush objects to disk to manage memory requirements of incoming requests. For example, session scoped objects, and even application scoped objects, are written to disk when required. While these application frameworks do the real work of writing objects to disk, they do not enforce that those objects be serializable, thus leaving the web application vulnerable to crashes induced by serialization failure. An attacker may be able to mount a denial of service attack by sending enough requests to the server to force the web application to save objects to disk.

취약점 도입 방식

Implementation

적용 가능한 플랫폼

언어

이름: Java (Undetermined)

기술

클래스: Web Based (Undetermined)
이름: Web Server (Undetermined)

일반적인 결과

잠재적 완화 방법

Phases : Architecture and Design // Implementation
All objects that become part of session and application scope must implement the java.io.Serializable interface to ensure serializability of containing objects.

취약점 매핑 메모

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

제출

수정 사항