Struts: Form Does Not Extend Validation Class - Revision history

KirstenS at 23:35, 7 April 2009

2009-04-07T23:35:37Z

KirstenS at 00:52, 18 February 2009

2009-02-18T00:52:02Z

KirstenS at 00:35, 6 November 2008

2008-11-06T00:35:42Z

KirstenS at 00:05, 1 October 2008

2008-10-01T00:05:11Z

Jeff Williams: /* Description */

2008-03-20T04:32:41Z

‎Description

Weilin Zhong: Contents provided by Fortify.

2006-07-24T18:17:31Z

Contents provided by Fortify.

New page

{{Template:Vulnerability}}
{{Template:Fortify}}

==Abstract==

All Struts forms should extend a Validator class.

==Description==

In order to use the Struts Validator, a form must extend one of the following:

<pre>
ValidatorForm
ValidatorActionForm
DynaValidatorActionForm
DynaValidaorForm.
</pre>

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:

<pre>
ActionForm
DynaActionForm
</pre>

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.

==Examples ==

==Related Threats==

==Related Attacks==

==Related Vulnerabilities==

==Related Countermeasures==

[[:Category:Input Validation]]

==Categories==

[[Category:Input Validation Vulnerability]]
[[Category:Struts]]
[[Category:Java]]
[[Category:Code Snippet]]
[[Category:Implementation]]

← Older revision		Revision as of 23:35, 7 April 2009
Line 4:		Line 4:


−	~~__TOC__~~
−
−	~~[[ASDR Table of Contents]]~~

@@ Line 1: / Line 1: @@
-{{Template:Vulnerability}}
+{{template:CandidateForDeletion}}
-{{Template:Fortify}}
 __TOC__
@@ Line 8: / Line 10: @@
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
@@ Line 75: / Line 74: @@
 __NOTOC__

@@ Line 2: / Line 2: @@
 {{Template:Fortify}}
-[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
+__TOC__
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
-[[ASDR Table of Contents]]
+[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
@@ Line 82: / Line 83: @@
 [[Category:Code Snippet]]
 [[Category:Implementation]]

@@ Line 2: / Line 2: @@
 {{Template:Fortify}}
-==Abstract==
+[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 ==Description==
 In order to use the Struts Validator, a form must extend one of the following:
@@ Line 28: / Line 36: @@
 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 Threats==
+==Risk Factors==
-==Related Attacks==
+TBD
-[[:Category:Input Validation]]
+__NOTOC__
 [[Category:Input Validation Vulnerability]]
 [[Category:Struts]]

@@ Line 14: / Line 14: @@
 	ValidatorActionForm
 	DynaValidatorActionForm
-	DynaValidaorForm.
+	DynaValidatorForm.
 </pre>