Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date.
View on MITREIt is easy for developers to forget to update validation logic when they make changes to an ActionForm class. One indication that validation logic is not being properly maintained is inconsistencies between the action form and the validation form. 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.
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.
No mitigation information available for this CWE.
To find the issue in the implementation, manual checks or automated static analysis could be applied to the XML configuration files.
To find the issue in the implementation, manual checks or automated static analysis could be applied to the XML configuration files.
This example shows an inconsistency between an action form and a validation form. with a third field.
This first block of code shows an action form that has two fields, startDate and endDate.
This example shows an inconsistency between an action form and a validation form. with a third field.
This first block of code shows an action form that has two fields, startDate and endDate.
No relationship information available for this CWE.
CWE-110: Struts: Validator Without Form Field is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date. It is easy for developers to forget to update validation logic when they make changes to an ActionForm class. One indication that validation logic is not being properly maintained is inconsistencies between the action form and the validation form. 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.
If exploited, CWE-110 (Struts: Validator Without Form Field) it can compromise Other, leading to outcomes such as Other.
CWE-110 can be detected using Automated Static Analysis and Manual Static Analysis. Combining automated tooling with manual review typically yields the best coverage.
CWE-110 commonly affects Java. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
A CWE (Common Weakness Enumeration) like CWE-110 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.