Name Fuzzing for garnering J2EE/.NET-based stack traces, for application mapping
Summary An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes any stack traces produced by error messages. Fuzzing techniques involve sending random or malformed messages to a target and monitoring the target's response. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to cause the targeted application to return an error including a stack trace, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash. The stack trace enumerates the chain of methods that led up to the point where the error was encountered. This can not only reveal the names of the methods (some of which may have known weaknesses) but possibly also the location of class files and libraries as well as parameter values. In some cases, the stack trace might even disclose sensitive configuration or user information.
Prerequisites The target application must fail to sanitize incoming messages adequately before processing and must generate a stack trace in at least some error situations.
Related Weaknesses
CWE ID Description
CWE-209 Generation of Error Message Containing Sensitive Information
CWE-388 7PK - Errors
Back to Top