This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Struts: Form Does Not Extend Validation Class"
Weilin Zhong (talk | contribs) (Contents provided by Fortify.) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{template:CandidateForDeletion}} |
| − | |||
| − | + | #REDIRECT [[Improper Data Validation]] | |
| + | |||
| + | |||
| + | |||
| + | |||
| + | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| − | |||
==Description== | ==Description== | ||
| + | |||
| + | All Struts forms should extend a Validator class. | ||
In order to use the Struts Validator, a form must extend one of the following: | In order to use the Struts Validator, a form must extend one of the following: | ||
| Line 14: | Line 19: | ||
ValidatorActionForm | ValidatorActionForm | ||
DynaValidatorActionForm | DynaValidatorActionForm | ||
| − | + | DynaValidatorForm. | |
</pre> | </pre> | ||
| Line 28: | Line 33: | ||
Bypassing the validation framework for a form exposes the application to numerous types of attacks. Unchecked input is the root cause of vulnerabilities like cross-site scripting, process control, and SQL injection. Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack. | Bypassing the validation framework for a form exposes the application to numerous types of attacks. Unchecked input is the root cause of vulnerabilities like cross-site scripting, process control, and SQL injection. Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack. | ||
| − | |||
| − | ==Related | + | ==Risk Factors== |
| + | |||
| + | TBD | ||
| + | |||
| + | ==Examples== | ||
| + | |||
| + | TBD | ||
| + | |||
| + | ==Related [[Attacks]]== | ||
| + | |||
| + | * [[Attack 1]] | ||
| + | * [[Attack 2]] | ||
| + | |||
| + | |||
| + | ==Related [[Vulnerabilities]]== | ||
| + | |||
| + | * [[Vulnerability 1]] | ||
| + | * [[Vulnerabiltiy 2]] | ||
| + | |||
| + | ==Related [[Controls]]== | ||
| + | |||
| + | * [[:Category:Input Validation]] | ||
| + | |||
| + | |||
| + | ==Related [[Technical Impacts]]== | ||
| + | |||
| + | * [[Technical Impact 1]] | ||
| + | * [[Technical Impact 2]] | ||
| − | |||
| − | == | + | ==References== |
| − | + | TBD | |
| − | |||
| − | |||
| − | + | __NOTOC__ | |
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 23:35, 7 April 2009
#REDIRECT Improper Data Validation
Last revision (mm/dd/yy): 04/7/2009
Description
All Struts forms should extend a Validator class.
In order to use the Struts Validator, a form must extend one of the following:
ValidatorForm ValidatorActionForm DynaValidatorActionForm DynaValidatorForm.
You must extend one of these classes because the Struts Validator ties in to your application by implementing the validate() method in these classes.
Forms derived from the following classes cannot use the Struts Validator:
ActionForm DynaActionForm
Bypassing the validation framework for a form exposes the application to numerous types of attacks. Unchecked input is the root cause of vulnerabilities like cross-site scripting, process control, and SQL injection. Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack.
Risk Factors
TBD
Examples
TBD
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
TBD
