CWE-1173 Improper Use of Validation Framework

The product does not use, or incorrectly uses, an input validation framework that is provided by the source language, framework, or an independent library.

• Integrity: Unexpected State — Unchecked input leads to cross-site scripting, process control, and SQL injection vulnerabilities, among others. • Other: Reduce Maintainability — Not using provided input validation frameworks can hurt the maintainability of code, since future developers may not recognize the downstream input validation that is required or expected in place of a validation framework.

• [Implementation] Properly use provided input validation frameworks.

• Automated Static Analysis: Some instances of improper input validation can be detected using automated static analysis. A static analysis tool might allow the user to specify which application-specific methods or functions perform input validation; the tool might also have built-in knowledge of validation frameworks such as Struts. The tool may then suppress or de-prioritize any associated warnings. This allows the analyst to focus on areas of the software in which input validation does not appear to be present. Except in the cases described in the previous paragraph, automated static analysis might not be able to recognize when proper input validation is being performed, leading to false positives - i.e., warnings that do not have any security consequences or require any code changes.