CWE-1174: ASP.NET Misconfiguration: Improper Model Validation
The ASP.NET application does not use, or incorrectly uses, the model validation framework.
View on MITRETechnical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Unchecked input leads to cross-site scripting, process control, and SQL injection vulnerabilities, among others.
Mitigation Strategies
No mitigation information available for this CWE.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
No examples or observed CVEs available for this CWE.
CWE Relationships
Frequently Asked Questions
What is CWE-1174: ASP.NET Misconfiguration: Improper Model Validation?+
CWE-1174: ASP.NET Misconfiguration: Improper Model Validation is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The ASP.NET application does not use, or incorrectly uses, the model validation framework.
What are the security consequences of ASP.NET Misconfiguration: Improper Model Validation?+
If exploited, CWE-1174 (ASP.NET Misconfiguration: Improper Model Validation) it can compromise Integrity, leading to outcomes such as Unexpected State.
Which programming languages are affected by ASP.NET Misconfiguration: Improper Model Validation?+
CWE-1174 commonly affects ASP.NET. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
What is the difference between a CWE and a CVE?+
A CWE (Common Weakness Enumeration) like CWE-1174 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.