Home > CAPEC List > CAPEC-214: Fuzzing for garnering J2EE/.NET-based stack traces, for application mapping (Version 2.10)  

CAPEC-214: Fuzzing for garnering J2EE/.NET-based stack traces, for application mapping

 
Fuzzing for garnering J2EE/.NET-based stack traces, for application mapping
Definition in a New Window Definition in a New Window
Attack Pattern ID: 214
Abstraction: Detailed
Status: Draft
Completeness: Stub
Presentation Filter:
+ 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.

+ Attack 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.

+ Typical Severity

Low

+ Resources Required

The attacker must have sufficient access to send messages to the target. The attacker must also have the ability to observe the stack trace produced by the target application. Fuzzing tools, which automatically generate and send message variants, are necessary for this attack.

+ Content History
Submissions
SubmitterOrganizationDateSource
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team
More information is available — Please select a different filter.
Page Last Updated or Reviewed: May 01, 2017