ASP.NET Misconfiguration: Not Using Input Validation Framework

Draft Variant
Structure: Simple
Description

This vulnerability occurs when an ASP.NET application fails to implement a structured input validation framework, relying instead on ad-hoc or missing validation checks.

Extended Description

ASP.NET provides built-in validation frameworks, like the Validator controls or model validation with Data Annotations, which automate the enforcement of security rules. When developers bypass these frameworks and write custom validation manually, they often introduce inconsistencies, miss critical checks, or fail to properly sanitize data across all entry points. This creates gaps where attackers can inject malicious input. Without a centralized validation strategy, the application becomes vulnerable to common attacks like SQL injection, cross-site scripting (XSS), and command injection. Using the framework ensures validation is applied consistently, reduces human error, and leverages security features that are maintained and updated by the platform. Adopting a structured approach is essential for building a robust security posture from the ground up.

Common Consequences 1
Scope: Integrity

Impact: Unexpected State

Unchecked input leads to cross-site scripting, process control, and SQL injection vulnerabilities, among others.

Potential Mitigations 1
Phase: 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
Applicable Platforms
Languages:
ASP.NET : Undetermined
Modes of Introduction
Architecture and Design
Implementation
Taxonomy Mapping
  • Software Fault Patterns