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 3357

3357 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-2024-32990 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.1 Medium2024-05-11
CVE-2024-32989 Huawei HarmonyOS 安全漏洞 — HarmonyOS 3.3 Low2024-05-11
CVE-2024-2257 Password Policy Bypass Vulnerability in Digisol Router — Digisol Router DG-GR1321 4.6 -2024-05-10
CVE-2024-32672 SAMSUNG Escargot 安全漏洞 — Escargot 5.3 Medium2024-05-09
CVE-2024-34365 Apache Karaf Cave: Cave SSRF and arbitrary file access — Apache Karaf Cave 9.1 -2024-05-09
CVE-2024-32669 Possible stack overflow due to a string encoding processing error — Escargot 5.3 Medium2024-05-09
CVE-2024-2746 Incomplete fix for CVE-2024-1929 — dnf5daemon-server 8.8 High2024-05-08
CVE-2024-1929 Local Root Exploit via Configuration Dictionary — dnf5daemon-server 7.5 High2024-05-08
CVE-2023-7240 Broken Access Control leading to SSRF in NetIQ Identity Console — NetIQ Identity Console 5.8 Medium2024-05-07
CVE-2024-21476 Improper Input Validation in Secure Processor — Snapdragon 7.8 High2024-05-06
CVE-2024-4548 Delta Electronics DIAEnergie SQL Injection — DIAEnergie 9.8 Critical2024-05-06
CVE-2024-4547 Delta Electronics DIAEnergie Unauthenticated SQL Injection — DIAEnergie 9.8 Critical2024-05-06
CVE-2024-20064 MediaTek 芯片 安全漏洞 — MT6580, MT6761, MT6762, MT6768, MT6781, MT6789, MT6833, MT6853, MT6853T, MT6855, MT6873, MT6875, MT6877, MT6879, MT6883, MT6885, MT6886, MT6889, MT6891, MT6893, MT6895, MT6983, MT6985, MT6989, MT8678, MT8755, MT8775, MT8792, MT8796 7.8AIHighAI2024-05-06
CVE-2024-20056 MediaTek 芯片 安全漏洞 — MT6739, MT6761, MT6765, MT6768, MT6781, MT6785, MT6789, MT6833, MT6835, MT6853, MT6855, MT6873, MT6880, MT6885, MT6886, MT6890, MT6893, MT6895, MT6897, MT6983, MT6985, MT6989, MT8666, MT8667, MT8673, MT8676, MT8678 6.7AIMediumAI2024-05-06
CVE-2023-40515 LG Simple Editor joinAddUser Improper Input Validation Denial-of-Service Vulnerability — Simple Editor 7.5 -2024-05-03
CVE-2023-32170 Unified Automation UaGateway OPC UA Server Improper Input Validation Denial-of-Service Vulnerability — UaGateway 6.5 -2024-05-03
CVE-2024-0710 GP Unique ID <= 1.5.5 - Unauthenticated Form Submission Unique ID Modification — GP Unique ID 5.3 Medium2024-05-02
CVE-2024-2751 Exclusive Addons for Elementor <= 2.6.9.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via InfoBox — Exclusive Addons for Elementor 6.4 Medium2024-05-02
CVE-2024-3747 Blocksy <= 2.0.39 - Authenticated (Contributor+) Stored Cross-Site Scripting via About Me block — Blocksy 6.4 Medium2024-05-02
CVE-2024-2867 Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress <= 4.15.4 - Authenticated (Contributor+) Stored Cross-Site Scripting — Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress 6.4 Medium2024-05-02
CVE-2024-4003 Essential Addons for Elementor – Best Elementor Templates, Widgets, Kits & WooCommerce Builders <= 5.9.15 - Authenticated (Contributor+) Stored Cross-Site Scripting — Essential Addons for Elementor – Popular Elementor Templates & Widgets 6.4 Medium2024-05-02
CVE-2024-4142 JFrog Artifactory Improper input validation within token creation flow — Artifactory 9.0 Critical2024-05-01
CVE-2024-23335 Backups directory .htaccess deletion in. MyBB — mybb 4.7 Medium2024-05-01
CVE-2024-3096 PHP function password_verify can erroneously return true when argument contains NUL — PHP 6.5 Medium2024-04-29
CVE-2024-2756 __Host-/__Secure- cookie bypass due to partial CVE-2022-31629 fix — PHP 6.5 Medium2024-04-29
CVE-2024-32646 vyper performs double eval of the slice args when buffer from adhoc locations — vyper 5.3 Medium2024-04-25
CVE-2024-32645 vyper performs incorrect topic logging in raw_log — vyper 5.3 Medium2024-04-25
CVE-2024-28240 GLPI-Agent's MSI package installation permits local users to change Agent configuration — glpi-agent 7.3 High2024-04-25
CVE-2024-4175 Improper Input Validation vulnerability in Hyperion Web Server — Hyperion Web Server 5.4 Medium2024-04-25
CVE-2024-25583 Crafted responses can lead to a denial of service in Recursor if recursive forwarding is configured — Recursor 7.5 High2024-04-25

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