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-2019-15613 Nextcloud Server 数据伪造问题漏洞 — Nextcloud Server 8.8 -2020-02-04
CVE-2020-8124 Url-Parse 输入验证错误漏洞 — url-parse 7.5 -2020-02-04
CVE-2020-8125 npm klona 输入验证错误漏洞 — klona npm module 9.8 -2020-02-04
CVE-2020-3147 Cisco Small Business Switches Denial of Service Vulnerability — Cisco Small Business 300 Series Managed Switches 7.5 -2020-01-29
CVE-2019-5464 GitLab 代码问题漏洞 — GitLab CE/EE 9.1 -2020-01-28
CVE-2019-16026 Cisco Mobility Management Entity Denial of Service Vulnerability — Cisco ASR 5000 Series Software 5.9 -2020-01-26
CVE-2020-3134 Cisco Email Security Appliance Zip Decompression Engine Denial of Service Vulnerability — Cisco Email Security Appliance (ESA) 7.5 -2020-01-26
CVE-2019-16029 Cisco Smart Software Manager On-Prem Web Interface Denial of Service Vulnerability — Cisco Smart Software Manager On-Prem 9.1 -2020-01-26
CVE-2019-16027 Cisco IOS XR Software Intermediate System–to–Intermediate System Denial of Service Vulnerability — Cisco IOS XR Software 6.5 -2020-01-26
CVE-2020-3139 Cisco Application Policy Infrastructure Controller Out Of Band Management IP Tables Bypass Vulnerability — Cisco Application Policy Infrastructure Controller (APIC) 5.3 -2020-01-26
CVE-2020-6962 多款GE产品输入验证错误漏洞 — GE CARESCAPE Telemetry Server,ApexPro Telemetry Server,CARESCAPE Central Station,Clinical Information Center,CARESCAPE B450,B650,B850 Monitors 10.0 -2020-01-24
CVE-2019-9503 Broadcom brcmfmac driver is vulnerable to a frame validation bypass — brcmfmac WiFi driver 7.9 High2020-01-16
CVE-2019-13524 多款GE产品输入验证错误漏洞 — GE PACSystems RX3i 7.5 -2020-01-16
CVE-2019-13939 多款Siemens产品输入验证错误漏洞 — APOGEE MEC/MBC/PXC (P2) 7.1 High2020-01-16
CVE-2019-15961 Clam AntiVirus (ClamAV) Software Email Parsing Vulnerability — ClamAV 7.5 High2020-01-15
CVE-2019-14866 cpio 安全漏洞 — cpio 7.8 -2020-01-07
CVE-2019-19337 Red Hat Ceph Storage 输入验证错误漏洞 — Ceph Storage 6.5 -2019-12-23
CVE-2019-18994 ABB PB610 HMIStudio crashes after launching an empty *.JPR application file — ABB PB610 Panel Builder 600 3.9 Low2019-12-18
CVE-2019-18995 ABB PB610 HMISimulator does not check content-length of the HTTP request — PB610 Panel Builder 600 4.3 Medium2019-12-18
CVE-2019-13932 Siemens XHQ Operations Intelligence 安全漏洞 — XHQ 8.2 -2019-12-12
CVE-2019-11255 Kubernetes CSI volume snapshot, cloning and resizing features can result in unauthorized volume data access or mutation — kubernetes-csi external-provisioner 4.8 Medium2019-12-05
CVE-2019-18247 ABB Relion 670 Series和ABB Relion 650 Series 输入验证错误漏洞 — Relion 650 and 670 Series 7.5 -2019-11-27
CVE-2019-15971 Cisco Email Security Appliance MP3 Content Filter Bypass Vulnerability — Cisco Email Security Appliance (ESA) 4.3 -2019-11-26
CVE-2019-15988 Cisco Email Security Appliance URL Filtering Bypass Vulnerability — Cisco Email Security Appliance (ESA) 5.3 -2019-11-26
CVE-2019-15997 Cisco DNA Spaces: Connector Command Injection Vulnerability — Cisco DNA Spaces 6.7 -2019-11-26
CVE-2019-15276 Cisco Wireless LAN Controller HTTP Parsing Engine Denial of Service Vulnerability — Cisco Wireless LAN Controller (WLC) 5.7 -2019-11-26
CVE-2019-15288 Cisco TelePresence Collaboration Endpoint, TelePresence Codec, and RoomOS Software Privilege Escalation Vulnerability — Cisco TelePresence TC Software 8.8 -2019-11-26
CVE-2019-15958 Cisco Prime Infrastructure and Evolved Programmable Network Manager Remote Code Execution Vulnerability — Cisco Prime Infrastructure 9.8 -2019-11-26
CVE-2019-11289 A forged route service request using an invalid nonce can cause the gorouter to panic and crash — Routing 8.6 -2019-11-19
CVE-2019-16762 Validator parsing discrepancy due to string encoding in NPM slpjs — slpjs 5.7 Medium2019-11-15

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