Weakness · Medium
CWE-110: Struts: Validator Without Form Field
What it is
Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date.
- Severity (our rating)
- Medium
- Likelihood of exploit
- Not rated by MITRE
- Introduced during
- Implementation, Operation
- Exploited in the wild
- No CVE in CISA's catalog
In more detail
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.
What an attacker can do
- Other (Other)
How to prevent it
MITRE lists no specific mitigation for this weakness. Treat it like its parent weaknesses below: validate input, keep the design simple and review the code where it could appear.
How to find 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.
- Manual Static Analysis. To find the issue in the implementation, manual checks or automated static analysis could be applied to the XML configuration files.
H2 Security
Found it in your code?
We review where it appears, fix it with your team, and check it was not already used against you.
Talk to our teamT Academy
Stop writing it in the first place
Learn to build software and systems without weaknesses like this one, with practice on real hosts in your browser, every objective checked on the machine.
Start freeSource: MITRE Common Weakness Enumeration, CWE version 4.19.1. CWE is a trademark of The MITRE Corporation.