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-2023-42661 JFrog Artifactory Improper input validation leads to arbitrary file write — Artifactory 7.2 High2024-03-07
CVE-2024-1534 Booster for WooCommerce <= 7.1.7 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortocde — Booster for WooCommerce – PDF Invoices, Abandoned Cart, Variation Swatches & 100+ Tools 6.4 Medium2024-03-07
CVE-2024-27932 Deno's improper suffix match testing for DENO_AUTH_TOKENS — deno 4.6 Medium2024-03-06
CVE-2024-27918 Coder's OIDC authentication allows email with partially matching domain to register — coder 8.2 High2024-03-06
CVE-2024-27931 Insufficient permission checking in `Deno.makeTemp*` APIs — deno 5.8 Medium2024-03-05
CVE-2023-33104 Improper input Validation in Multi-Mode Call Processor — Snapdragon 7.5 High2024-03-04
CVE-2023-33103 Improper Input Validation in Multi-Mode Call Processor — Snapdragon 7.5 High2024-03-04
CVE-2023-28578 Improper Input Validation in Services — Snapdragon 9.3 Critical2024-03-04
CVE-2024-25016 IBM MQ denial of service — MQ 7.5 High2024-03-03
CVE-2023-50737 An input validation vulnerability in the SE Menu allows an attacker to execute arbitrary code. — various 9.1 Critical2024-02-28
CVE-2023-51747 SMTP smuggling in Apache James — Apache James server 7.5 -2024-02-27
CVE-2024-27093 Minder trusts client-provided mapping from repo name to upstream ID — minder 4.6 Medium2024-02-26
CVE-2024-27092 Content spoofing - real Hoppscotch emails — hoppscotch 5.4 Medium2024-02-26
CVE-2024-23320 Apache DolphinScheduler: Arbitrary js execution as root for authenticated users — Apache DolphinScheduler 5.4 -2024-02-23
CVE-2024-26151 Potentially untrusted input is rendered as HTML in final output — mjml-python 8.2 High2024-02-22
CVE-2024-1714 Access Request for Entitlement Values with Leading/Trailing Whitespace — IdentityIQ 7.1 High2024-02-21
CVE-2024-25974 Stored Cross-Site Scripting (XSS) within the Media Center — OpenOlat LMS 5.4AIMediumAI2024-02-20
CVE-2024-25973 Multiple Stored Cross-Site Scripting Vulnerabilities — OpenOlat LMS 5.4AIMediumAI2024-02-20
CVE-2024-1638 Bluetooth characteristic LESC security requirement not enforced without additional flags — Zephyr 8.2 High2024-02-19
CVE-2023-52372 Huawei EMUI 安全漏洞 — HarmonyOS 4.9AIMediumAI2024-02-18
CVE-2023-52368 Huawei EMUI 安全漏洞 — HarmonyOS--AI2024-02-18
CVE-2023-6937 Improper (D)TLS key boundary enforcement — wolfSSL 5.3 Medium2024-02-15
CVE-2023-32484 Dell EMC Enterprise SONiC 输入验证错误漏洞 — Enterprise SONiC OS 9.8 Critical2024-02-15
CVE-2023-32462 Dell OS10 Networking Switches 输入验证错误漏洞 — Dell SmartFabric OS10 9.8 Critical2024-02-15
CVE-2024-20733 [ZS-VR-23-360] Adobe Acrobat Reader Parsing OTF font Denial-of-Service Vulnerability — Acrobat Reader 5.5 Medium2024-02-15
CVE-2024-1471 HTML Injection Vulnerability — Security Center 5.9 Medium2024-02-14
CVE-2024-24696 Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for Windows - Improper Input Validation — Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for Windows 6.8 Medium2024-02-13
CVE-2024-24695 Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for Windows - Improper Input Validation — Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for Windows 6.8 Medium2024-02-13
CVE-2024-1378 Command injection vulnerability was identified in GitHub Enterprise Server that allowed privilege escalation in the Mangement Console — Enterprise Server 9.1 Critical2024-02-13
CVE-2024-1374 Command injection vulnerability was identified in GitHub Enterprise Server that allowed privilege escalation in the Mangement Console — Enterprise Server 9.1 Critical2024-02-13

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