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-21312 .NET Framework Denial of Service Vulnerability — Microsoft .NET Framework 3.5 AND 4.8.1 7.5 High2024-01-09
CVE-2024-21316 Windows Server Key Distribution Service Security Feature Bypass — Windows 10 Version 1809 6.1 Medium2024-01-09
CVE-2024-0057 NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability — .NET 8.0 9.1 Critical2024-01-09
CVE-2024-20666 BitLocker Security Feature Bypass Vulnerability — Windows 10 Version 1809 6.6 Medium2024-01-09
CVE-2024-22165 Denial of Service in Splunk Enterprise Security of the Investigations manager through Investigation creation — Splunk Enterprise Security (ES) 6.5 Medium2024-01-09
CVE-2023-51438 Siemens SIMATIC IPC1047E 安全漏洞 — SIMATIC IPC1047E 10.0 Critical2024-01-09
CVE-2023-49252 Siemens SIMATIC CN 4100 输入验证错误漏洞 — SIMATIC CN 4100 7.5 High2024-01-09
CVE-2024-21663 Remote code execution on ReconServer due to improper input sanitization on the prips command — Discord-Recon 10.0 Critical2024-01-08
CVE-2023-41782 DLL Hijacking Vulnerability in ZTE ZXCLOUD iRAI — ZXCLOUD iRAI 3.9 Low2024-01-05
CVE-2024-21625 One-click remote code execution via malicious deep link — SideQuest 8.8 High2024-01-04
CVE-2023-6992 Memory corruption issues is Cloudflare zlib implementation — zlib 4.0 Medium2024-01-04
CVE-2023-6738 PageLayer <= 1.7.8 - Authenticated(Contributor+) Stored Cross-Site Scripting via meta fields — Page Builder: Pagelayer – Drag and Drop website builder 5.4 Medium2024-01-04
CVE-2023-50256 Froxlor username/surname AND company field Bypass — Froxlor 7.5 High2024-01-03
CVE-2024-21631 Integer overflow in URI leading to potential host spoofing — vapor 6.5 Medium2024-01-03
CVE-2023-33014 Improper Input Validation in Services — Snapdragon 7.6 High2024-01-02
CVE-2023-26159 Follow Redirects 安全漏洞 — follow-redirects 7.3 High2024-01-02
CVE-2023-49299 Apache DolphinScheduler: Arbitrary js execute as root for authenticated users — Apache DolphinScheduler 8.2 -2023-12-30
CVE-2023-52137 GitHub Action tj-actions/verify-changed-files is vulnerable to command injection in output filenames — verify-changed-files 7.7 High2023-12-29
CVE-2023-47804 Apache OpenOffice: Macro URL arbitrary script execution — Apache OpenOffice 7.8 -2023-12-29
CVE-2023-7163 D-Link D-View 8 Unauthenticated Probe-Core Server Communication — D-View 8 10.0 Critical2023-12-28
CVE-2023-6879 heap buffer overflow in libaom — libaom 9.0 Critical2023-12-27
CVE-2023-39251 Dell BIOS 安全漏洞 — CPG BIOS 6.7 Medium2023-12-22
CVE-2023-45165 IBM AIX denial of service — AIX 6.2 Medium2023-12-22
CVE-2023-6784 Potential Use of the Sitefinity System for Distribution of Phishing Emails — Sitefinity 4.7 Medium2023-12-20
CVE-2023-0011 Command Execution through Serial Interface of u-blox TOBY-L2 — TOBY-L2 7.6 High2023-12-20
CVE-2023-47705 IBM Security Guardium Key Lifecycle Manager improper input validation — Security Guardium Key Lifecycle Manager 4.3 Medium2023-12-20
CVE-2023-47161 IBM UrbanCode Deploy denial of service — UrbanCode Deploy 5.3 Medium2023-12-19
CVE-2023-42012 IBM UrbanCode Deploy denial of service — UrbanCode Deploy 6.2 Medium2023-12-19
CVE-2023-45172 IBM AIX denial of service — AIX 6.2 Medium2023-12-19
CVE-2023-22439 Gallagher Controller 6000 输入验证错误漏洞 — Controller 6000/ Controller 7000 3.1 Low2023-12-18

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