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 3361

3361 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-2020-3496 Cisco Small Business Smart and Managed Switches Denial of Service Vulnerability — Cisco Small Business 250 Series Smart Switches Software 7.5 -2020-08-26
CVE-2020-3506 Cisco Video Surveillance 8000 Series IP Cameras Cisco Discovery Protocol Remote Code Execution and Denial of Service Vulnerabilities — Cisco Video Surveillance 8000 Series IP Cameras 8.8 High2020-08-26
CVE-2020-3507 Cisco Video Surveillance 8000 Series IP Cameras Cisco Discovery Protocol Remote Code Execution and Denial of Service Vulnerabilities — Cisco Video Surveillance 8000 Series IP Cameras 8.8 High2020-08-26
CVE-2020-3519 Cisco Data Center Network Manager Path Traversal Vulnerability — Cisco Data Center Network Manager 8.1 -2020-08-26
CVE-2020-3521 Cisco Data Center Network Manager Read File Path Traversal Vulnerability — Cisco Data Center Network Manager 5.3 Medium2020-08-26
CVE-2019-14904 Ansible solaris_zone模块操作系统命令注入漏洞 — Ansible 7.3 -2020-08-25
CVE-2020-17393 Corel Parallels Desktop 输入验证错误漏洞 — Desktop 6.5 -2020-08-25
CVE-2020-16237 Philips SureSigns VS4 Improper Input Validation — SureSigns VS4 2.1 Low2020-08-21
CVE-2020-10289 RVD#2401: Use of unsafe yaml load, ./src/actionlib/tools/library.py:132 — ros 9.8 -2020-08-20
CVE-2020-3363 Cisco Small Business Smart and Managed Switches Denial of Service Vulnerability — Cisco Small Business 250 Series Smart Switches Software 7.5 -2020-08-17
CVE-2020-3434 Cisco AnyConnect Secure Mobility Client for Windows Denial of Service Vulnerability — Cisco AnyConnect Secure Mobility Client 5.5 Medium2020-08-17
CVE-2020-3435 Cisco AnyConnect Secure Mobility Client for Windows Profile Modification Vulnerability — Cisco AnyConnect Secure Mobility Client 5.5 Medium2020-08-17
CVE-2020-3501 Cisco Webex Meetings Desktop App Information Disclosure Vulnerabilities — Cisco Webex Meetings 4.1 Medium2020-08-17
CVE-2020-3502 Cisco Webex Meetings Desktop App Information Disclosure Vulnerabilities — Cisco Webex Meetings 4.1 Medium2020-08-17
CVE-2020-2035 PAN-OS: URL filtering policy is not enforced on TLS handshakes for decrypted HTTPS sessions — PAN-OS 3.0 Low2020-08-12
CVE-2020-16227 Delta Electronics TPEditor 输入验证错误漏洞 — Delta Electronics TPEditor 7.8 -2020-08-06
CVE-2020-15112 Improper Input Validation in etcd — etcd 6.5 Medium2020-08-05
CVE-2020-15106 Improper Input Validation in etcd — etcd 6.5 Medium2020-08-05
CVE-2020-15109 Ability to change order address without triggering address validations in solidus — solidus 5.3 Medium2020-08-04
CVE-2020-7823 DaviewIndy Multiple Vulnerabilities — DaviewIndy 7.8 High2020-08-04
CVE-2020-7822 DaviewIndy Multiple Vulnerabilities — DaviewIndy 7.8 High2020-08-04
CVE-2020-3383 Cisco Data Center Network Manager Path Traversal Vulnerability — Cisco Data Center Network Manager 8.8 High2020-07-31
CVE-2020-15086 Potential Remote Code Execution in TYPO3 with mediace extension — mediace 9.8 Critical2020-07-29
CVE-2020-7518 Schneider Electric Easergy Builder 输入验证错误漏洞 — Easergy Builder (Version 1.4.7.2 and older) 5.5 -2020-07-23
CVE-2020-10922 C-More HMI EA9 输入验证错误漏洞 — HMI EA9 7.5 -2020-07-23
CVE-2020-3452 Cisco Adaptive Security Appliance Software and Firepower Threat Defense Software Web Services Read-Only Path Traversal Vulnerability — Cisco Adaptive Security Appliance (ASA) Software 7.5 High2020-07-22
CVE-2020-12029 Rockwell Automation FactoryTalk View SE — FactoryTalk View SE 9.0 Critical2020-07-20
CVE-2020-7818 DaviewIndy Heap Overflow Vulnerability — DaviewIndy 7.8 High2020-07-17
CVE-2020-5131 SonicWall NetExtender Windows client 输入验证错误漏洞 — SonicWall NetExtender 7.8 -2020-07-17
CVE-2020-5130 SonicWall SonicOS 输入验证错误漏洞 — SonicOS 7.5 -2020-07-17

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