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 "Improper Data Validation"
(→Description) |
|||
| Line 14: | Line 14: | ||
==Description== | ==Description== | ||
| + | ===Struts: Duplicate Validation Forms=== | ||
Multiple validation forms with the same name indicate that validation logic is not up-to-date. | Multiple validation forms with the same name indicate that validation logic is not up-to-date. | ||
If two validation forms have the same name, the Struts Validator arbitrarily chooses one of the forms to use for input validation and discards the other. This decision might not correspond to the programmer's expectations. Moreover, it indicates that the validation logic is not being maintained, and can indicate that other, more subtle, validation errors are present. | If two validation forms have the same name, the Struts Validator arbitrarily chooses one of the forms to use for input validation and discards the other. This decision might not correspond to the programmer's expectations. Moreover, it indicates that the validation logic is not being maintained, and can indicate that other, more subtle, validation errors are present. | ||
| − | |||
| − | |||
==Risk Factors== | ==Risk Factors== | ||
Revision as of 00:41, 18 February 2009
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
- This article includes content generously donated to OWASP by
Last revision (mm/dd/yy): 02/18/2009
Description
Struts: Duplicate Validation Forms
Multiple validation forms with the same name indicate that validation logic is not up-to-date.
If two validation forms have the same name, the Struts Validator arbitrarily chooses one of the forms to use for input validation and discards the other. This decision might not correspond to the programmer's expectations. Moreover, it indicates that the validation logic is not being maintained, and can indicate that other, more subtle, validation errors are present.
Risk Factors
TBD
Examples
Two validation forms with the same name.
<form-validation> <formset> <form name="ProjectForm"> ... </form> <form name="ProjectForm"> ... </form> </formset> </form-validation>
It is critically important that validation logic be maintained and kept in sync with the rest of the application. Unchecked input is the root cause of some of today's worst and most common software security problems. Cross-site scripting, SQL injection, and process control vulnerabilities all stem from incomplete or absent input validation. 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
