Improper Use of Validation Framework

Opis

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

Many modern coding languages provide developers with input validation frameworks to make the task of input validation easier and less error-prone. These frameworks will automatically check all input against specified criteria and direct execution to error handlers when invalid input is received. The improper use (i.e., an incorrect implementation or missing altogether) of these frameworks is not directly exploitable, but can lead to an exploitable condition if proper input validation is not performed later in the product. Not using provided input validation frameworks can also hurt the maintainability of code as future developers may not recognize the downstream input validation being used in the place of the validation framework.

Skutki

• Integrity

  Unexpected State

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

Zapobieganie

• Implementation

  Properly use provided input validation frameworks.

Słabość nadrzędna

• CWE-20 Improper Input Validation

Słabości podrzędne

• CWE-102 Struts: Duplicate Validation Forms
• CWE-105 Struts: Form Field Without Validator
• CWE-106 Struts: Plug-in Framework not in Use
• CWE-108 Struts: Unvalidated Action Form
• CWE-109 Struts: Validator Turned Off
• CWE-554 ASP.NET Misconfiguration: Not Using Input Validation Framework
• CWE-1174 ASP.NET Misconfiguration: Improper Model Validation

Kiedy powstaje

• Architecture and Design — This weakness may occur when software designers choose to not leverage input validation frameworks provided by the source language.
• Implementation — This weakness may occur when developers do not correctly use a provided input validation framework.

Dotyczy

Not Language-Specific