Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CWE-20 (输入验证不恰当) — Vulnerability Class 3320

3320 vulnerabilities classified as CWE-20 (输入验证不恰当). AI Chinese analysis included.

CWE-20 represents a critical software weakness where applications fail to properly verify the integrity, format, or type of incoming data before processing it. This oversight allows attackers to inject malicious payloads, such as SQL injection strings or cross-site scripting code, which can bypass security controls and compromise system integrity. Exploitation typically occurs when untrusted data from external sources, like user forms or network packets, is treated as executable code or trusted input. To mitigate this risk, developers must implement rigorous input validation strategies, including strict type checking, length constraints, and allow-listing acceptable characters. Additionally, employing parameterized queries and output encoding ensures that even if validation fails, the injected data remains inert, thereby preserving application security and preventing unauthorized execution or data exposure.

MITRE CWE Description
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Input validation is a frequently-used technique for checking potentially dangerous inputs in order to ensure that the inputs are safe for processing within the code, or when communicating with other components. Input can consist of: raw data - strings, numbers, parameters, file contents, etc. metadata - information about the raw data, such as headers or size Data can be simple or structured. Structured data can be composed of many nested layers, composed of combinations of metadata and raw data, with other simple or structured data. Many properties of raw data or metadata may need to be validated upon entry into the code, such as: specified quantities such as size, length, frequency, price, rate, number of operations, time, etc. implied or derived quantities, such as the actual size of a file instead of a specified size indexes, offsets, or positions into more complex data structures symbolic keys or other elements into hash tables, associative arrays, etc. well-formedness, i.e. syntactic correctness - compliance with expected syntax lexical token correctness - compliance with rules for what is treated as a token specified or derived type - the actual type of the input (or what the input appears to be) consistency - between individual data el…
Common Consequences (3)
AvailabilityDoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory)
An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.
ConfidentialityRead Memory, Read Files or Directories
An attacker could read confidential data if they are able to control resource references.
Integrity, Confidentiality, AvailabilityModify Memory, Execute Unauthorized Code or Commands
An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.
Mitigations (5)
Architecture and DesignConsider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build "recognizers" for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subjec…
Architecture and DesignUse an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
Architecture and Design, ImplementationUnderstand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may b…
ImplementationAssume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range…
Effectiveness: High
Architecture and DesignFor any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server. Even though clien…
Examples (2)
This example demonstrates a shopping interaction in which the user is free to specify the quantity of items to be purchased and a total is calculated.
... public static final double price = 20.00; int quantity = currentUser.getAttribute("quantity"); double total = price * quantity; chargeUser(total); ...
Bad · Java
This example asks the user for a height and width of an m X n game board with a maximum dimension of 100 squares.
... #define MAX_DIM 100 ... /* board dimensions */ int m,n, error; board_square_t *board; printf("Please specify the board height: \n"); error = scanf("%d", &m); if ( EOF == error ){ die("No integer passed: Die evil hacker!\n"); } printf("Please specify the board width: \n"); error = scanf("%d", &n); if ( EOF == error ){ die("No integer passed: Die evil hacker!\n"); } if ( m > MAX_DIM || n > MAX_DIM ) { die("Value too large: Die evil hacker!\n"); } board = (board_square_t*) malloc( m * n * sizeof(board_square_t)); ...
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2026-21686 iccDEV has Undefined Behavior in CIccTagLutAtoB::Validate() — iccDEV 7.1 High2026-01-07
CVE-2026-21685 iccDEV has Undefined Behavior in CIccTagLut16::Read() — iccDEV 7.1 High2026-01-07
CVE-2026-21684 iccDEV has Undefined Behavior in CIccTagSpectralViewingConditions() — iccDEV 7.1 High2026-01-07
CVE-2026-21683 iccDEV has Type Confusion in icStatusCMM::CIccEvalCompare::EvaluateProfile() — iccDEV 8.8 High2026-01-07
CVE-2026-21682 iccDEV has heap-buffer-overflow in CIccXmlArrayType::ParseText() — iccDEV 8.8 High2026-01-07
CVE-2026-21681 iccDEV has Undefined Behavior runtime error: nan is outside the range .. IccProfLib/IccTagBasic.cpp — iccDEV 7.1 High2026-01-07
CVE-2026-21679 iccDEV has heap-buffer-overflow vulnerability in CIccLocalizedUnicode::GetText() — iccDEV 8.8 High2026-01-07
CVE-2026-21678 iccDEV has heap-buffer-overflow vulnerability on IccTagXml() — iccDEV 7.8 High2026-01-07
CVE-2026-21506 iccDEV is Vulnerable to Null Pointer Dereference in CIccProfileXml::ParseBasic() Leading to Denial of Service — iccDEV 5.5 Medium2026-01-07
CVE-2026-21505 iccDEV has Undefined Behavior (UB) - Invalid Enum Value — iccDEV 5.5 Medium2026-01-07
CVE-2026-21503 iccDEV has Undefined Behavior - Null Pointer Passed to memcpy() in CIccTagSparseMatrixArray — iccDEV 6.1 Medium2026-01-07
CVE-2026-21501 Stack Overflow in iccDEV Calculator Parser — iccDEV 5.5 Medium2026-01-07
CVE-2026-21502 NULL Pointer Dereference in iccDEV XML Tag Parser — iccDEV 5.5 Medium2026-01-07
CVE-2026-21500 Stack Overflow in iccDEV XML Calculator Macro Expansion — iccDEV 5.5 Medium2026-01-07
CVE-2026-21499 NULL Pointer Dereference in iccDEV XML Parser — iccDEV 5.5 Medium2026-01-07
CVE-2026-21498 NULL Pointer Dereference in iccDEV XML Calculator Parser — iccDEV 5.5 Medium2026-01-07
CVE-2026-21496 NULL Pointer Dereference in iccDEV Signature Parser — iccDEV 5.5 Medium2026-01-07
CVE-2026-21497 NULL Pointer Dereference in iccDEV Unknown Tag Parser — iccDEV 5.5 Medium2026-01-07
CVE-2026-21495 Division by Zero in iccDEV TIFF Image Reader — iccDEV 5.5 Medium2026-01-07
CVE-2025-12543 Undertow-core: undertow http server fails to reject malformed host headers leading to potential cache poisoning and ssrf — Red Hat build of Apache Camel 4.14.4 for Spring Boot 3.5.11 9.6 Critical2026-01-07
CVE-2026-21487 iccDEV has Out-of-bounds Read, Use of Out-of-range Pointer Offset and Improper Input Validation — iccDEV 6.1 Medium2026-01-06
CVE-2026-21485 iccDEV Undefined Behavior (UB) and Out of Memory in CIccProfile::LoadTag() — iccDEV 8.8 High2026-01-06
CVE-2025-61916 Spinnaker vulnerable to SSRF due to improper restrictions on http from user input — spinnaker 7.9 High2026-01-05
CVE-2025-69288 Titra has Remote Code Execution in Admin Functionality — titra 9.1 Critical2025-12-31
CVE-2025-15358 DVP-12SE11T - Denial of Service Vulnerability — DVP-12SE11T 7.5 High2025-12-30
CVE-2025-15284 arrayLimit bypass in bracket notation allows DoS via memory exhaustion 3.7 Low2025-12-29
CVE-2025-69205 In µURU, a Specially Crafted Federation Name Allows Dialplan Injection — uURU 6.3 Medium2025-12-29
CVE-2025-8075 Improper Input Validation — QNV-C8012 6.1 -2025-12-26
CVE-2025-52600 Improper Input Validation — QNV-C8012 9.3 -2025-12-26
CVE-2025-8769 MegaSys Computer Technologies Telenium Online Web Application Improper Input Validation — Telenium Online Web Application 9.8 Critical2025-12-24

Vulnerabilities classified as CWE-20 (输入验证不恰当) represent 3320 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.