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"
Weilin Zhong (talk | contribs) |
Weilin Zhong (talk | contribs) (Contents provided by Fortify.) |
||
| Line 1: | Line 1: | ||
{{Template:Vulnerability}} | {{Template:Vulnerability}} | ||
| + | {{Template:Fortify}} | ||
| + | |||
| + | ==Abstract== | ||
| + | |||
| + | This action form mapping disables the form's validate() method. | ||
==Description== | ==Description== | ||
| + | |||
| + | 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. | ||
==Examples == | ==Examples == | ||
| + | |||
| + | An action form mapping that disables validation. | ||
| + | |||
| + | <pre> | ||
| + | <action path="/download" | ||
| + | type="com.website.d2.action.DownloadAction" | ||
| + | name="downloadForm" | ||
| + | scope="request" | ||
| + | input=".download" | ||
| + | validate="false"> | ||
| + | </action> | ||
| + | </pre> | ||
| + | |||
| + | 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 Threats== | ==Related Threats== | ||
| Line 12: | Line 33: | ||
==Related Countermeasures== | ==Related Countermeasures== | ||
| + | |||
| + | [[:Category:Input Validation]] | ||
==Categories== | ==Categories== | ||
| − | |||
| − | |||
[[Category:Input Validation Vulnerability]] | [[Category:Input Validation Vulnerability]] | ||
| − | |||
[[Category:Struts]] | [[Category:Struts]] | ||
| + | [[Category:Java]] | ||
| + | [[Category:Code Snippet]] | ||
| + | [[Category:Implementation]] | ||
Revision as of 18:24, 24 July 2006
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
- This article includes content generously donated to OWASP by
Abstract
This action form mapping disables the form's validate() method.
Description
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.
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.
