CWE-110: Struts: Validator Without Form Field
Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date.
Last updated
Overview
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.
Common consequences
What can happen when CWE-110 is exploited.
Other
Affects: Other
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.
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
Applies to
Languages
How to detect it
Automated Static Analysis
To find the issue in the implementation, manual checks or automated static analysis could be applied to the XML configuration files.
Effectiveness: Moderate
Manual Static Analysis
To find the issue in the implementation, manual checks or automated static analysis could be applied to the XML configuration files.
Effectiveness: Moderate
Code examples
Illustrative examples from MITRE showing how the weakness appears in code.
This example shows an inconsistency between an action form and a validation form. with a third field.
Vulnerable example
public class DateRangeForm extends ValidatorForm {Vulnerable example
<form name="DateRangeForm">Terminology & mappings
Mapped taxonomies
- 7 Pernicious Kingdoms: Struts: Validator Without Form Field
- Software Fault Patterns: Tainted input to command (SFP24)
Frequently asked questions
Common questions about CWE-110.
- What is CWE-110?
- Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date.
- How is CWE-110 detected?
- Automated Static Analysis: To find the issue in the implementation, manual checks or automated static analysis could be applied to the XML configuration files.
- What are the consequences of CWE-110?
- Exploiting CWE-110 can lead to: Other.
References
- MITRE CWE definition (CWE-110) (opens in a new tab)
- CWE-110 vulnerabilities on NVD (opens in a new tab)
- Learn: What is a CWE?
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Stay ahead of CWE-110
Get alerted the moment a new CWE-110 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.