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: Plug-in Framework Not In Use"
Weilin Zhong (talk | contribs) (Contents provided by Fortify.) |
Weilin Zhong (talk | contribs) (→Categories) |
||
| Line 35: | Line 35: | ||
[[Category:Struts]] | [[Category:Struts]] | ||
[[Category:Java]] | [[Category:Java]] | ||
| − | |||
[[Category:Implementation]] | [[Category:Implementation]] | ||
Revision as of 18:20, 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
Use the Struts Validator to prevent vulnerabilities that result from unchecked input.
Description
Unchecked input is the leading cause of vulnerabilities in J2EE applications. Unchecked input leads to cross-site scripting, process control, and SQL injection vulnerabilities, among others. 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.
To prevent such attacks, use the Struts Validator to check all program input before it is processed by the application. Use the Fortify Source Code Analysis Engine to ensure that there are no holes in your configuration of the Struts Validator.
Example uses of the validator include checking to ensure that:
- Phone number fields contain only valid characters in phone numbers
- Boolean values are only "T" or "F"
- Free-form strings are of a reasonable length and composition
