CWE-554 ASP.NET Misconfiguration: Not Using Input Validation Framework

The ASP.NET application does not use an input validation framework.

• Integrity: Unexpected State — Unchecked input leads to cross-site scripting, process control, and SQL injection vulnerabilities, among others.

• [Architecture and Design] Use the ASP.NET validation framework to check all program input before it is processed by the application. Example uses of the validation framework include checking to ensure that: • Phone number fields contain only valid characters in phone numbers • Boolean values are only "T" or "F" • Free-form strings are of a reasonable length and composition

• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)