CWE-1173 Details

CWE-1173

Improper Use of Validation Framework
Draft
2019-01-03
00h00 +00:00
2023-06-29
00h00 +00:00
Benachrichtigungen für ein CWE
Bleiben Sie über alle Änderungen zu einem bestimmten CWE informiert.
Benachrichtigungen verwalten

Name: Improper Use of Validation Framework

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

CWE-Beschreibung

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.

Allgemeine Informationen

Einführungsmodi

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.

Anwendbare Plattformen

Sprache

Class: Not Language-Specific (Undetermined)

Häufige Konsequenzen

Bereich Auswirkung Wahrscheinlichkeit
IntegrityUnexpected State

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

Mögliche Gegenmaßnahmen

Phases : Implementation
Properly use provided input validation frameworks.

Erkennungsmethoden

Automated Static Analysis

Hinweise zur Schwachstellen-Zuordnung

Begründung : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Kommentar : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Einreichung

Name Organisation Datum Veröffentlichungsdatum Version
CWE Content Team MITRE 2018-12-21 +00:00 2019-01-03 +00:00 3.2

Änderungen

Name Organisation Datum Kommentar
CWE Content Team MITRE 2020-02-24 +00:00 updated Relationships
CWE Content Team MITRE 2020-06-25 +00:00 updated Relationships
CWE Content Team MITRE 2021-10-28 +00:00 updated Relationships
CWE Content Team MITRE 2023-01-31 +00:00 updated Description
CWE Content Team MITRE 2023-04-27 +00:00 updated Relationships
CWE Content Team MITRE 2023-06-29 +00:00 updated Mapping_Notes