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: Unused Validation Form"

From OWASP
Jump to: navigation, search
 
(Contents provided by Fortify.)
Line 1: Line 1:
 
{{Template:Vulnerability}}
 
{{Template:Vulnerability}}
 +
{{Template:Fortify}}
 +
 +
==Abstract==
 +
 +
An unused validation form indicates that validation logic is not up-to-date.
  
 
==Description==
 
==Description==
 +
 +
It is easy for developers to forget to update validation logic when they remove or rename action form mappings. One indication that validation logic is not being properly maintained is the presence of an unused validation form.
  
 
==Examples ==
 
==Examples ==
Line 12: Line 19:
  
 
==Related Countermeasures==
 
==Related Countermeasures==
 +
 +
[[:Category:Input Validation]]
  
 
==Categories==
 
==Categories==
 
{{Template:Stub}}
 
  
 
[[Category:Input Validation Vulnerability]]
 
[[Category:Input Validation Vulnerability]]
 
 
[[Category:Struts]]
 
[[Category:Struts]]
 +
[[Category:Java]]
 +
[[Category:Implementation]]

Revision as of 18:22, 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 MicroFocus Logo.png

Abstract

An unused validation form indicates that validation logic is not up-to-date.

Description

It is easy for developers to forget to update validation logic when they remove or rename action form mappings. One indication that validation logic is not being properly maintained is the presence of an unused validation form.

Examples

Related Threats

Related Attacks

Related Vulnerabilities

Related Countermeasures

Category:Input Validation

Categories