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: Validator Turned Off"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
{{Template:Vulnerability}}
+
{{template:CandidateForDeletion}}
{{Template:Fortify}}
+
 
 +
#REDIRECT [[Improper Data Validation]]
 +
 
  
 
__TOC__
 
__TOC__
Line 8: Line 10:
  
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 
 
  
 
==Description==
 
==Description==
Line 69: Line 68:
  
 
__NOTOC__
 
__NOTOC__
 
 
[[Category:OWASP ASDR Project]]
 
[[Category:Input Validation Vulnerability]]
 
[[Category:Struts]]
 
[[Category:Java]]
 
[[Category:Code Snippet]]
 
[[Category:Implementation]]
 
[[Category:Vulnerability]]
 

Revision as of 01:16, 18 February 2009

Template:CandidateForDeletion

#REDIRECT Improper Data Validation


ASDR Table of Contents


Last revision (mm/dd/yy): 02/18/2009

Description

This action form mapping disables the form's validate() method.

An action form mapping should never disable validation. Disabling validation disables the Struts Validator as well as any custom validation logic performed by the form.


Risk Factors

TBD

Examples

An action form mapping that disables validation.

	<action path="/download"
		type="com.website.d2.action.DownloadAction"
		name="downloadForm"
		scope="request"
		input=".download"
		validate="false">
	</action>

Disabling validation exposes this action 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 Attacks


Related Vulnerabilities

Related Controls


Related Technical Impacts


References

TBD