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-2018-1060 Python 资源管理错误漏洞 — python 7.5 -2018-06-18
CVE-2018-1070 routing 安全漏洞 — routing 6.5 -2018-06-12
CVE-2018-0338 Cisco Unified Computing System Software 输入验证错误漏洞 — Cisco Unified Computing System unknown 7.8 -2018-06-07
CVE-2018-0355 Cisco Unified Communications Manager 输入验证错误漏洞 — Cisco Unified Communications Manager unknown 6.1 -2018-06-07
CVE-2018-0274 Cisco Network Services Orchestrator CLI解析器输入验证漏洞 — Cisco Network Services Orchestrator unknown 8.8 -2018-06-07
CVE-2018-0296 多款Cisco产品ASA Software和Firepower Threat Defense Software 输入验证错误漏洞 — Cisco Adaptive Security Appliance unknown 7.5 -2018-06-07
CVE-2017-16226 The static-eval 输入验证错误漏洞 — static-eval node module node module 9.8 -2018-06-07
CVE-2017-7653 Eclipse Mosquitto broker 安全漏洞 — Eclipse Mosquitto 7.5 -2018-06-05
CVE-2017-16005 Http-signature 安全漏洞 — http-signature node module 7.5 -2018-06-04
CVE-2016-10543 call 安全漏洞 — call node module 5.3 -2018-05-31
CVE-2016-10555 jwt-simple 安全漏洞 — jwt-simple node module 6.5 -2018-05-31
CVE-2015-9235 jsonwebtoken node模块安全漏洞 — jsonwebtoken node module 9.8 -2018-05-29
CVE-2017-2617 hawtio 输入验证漏洞 — hawtio 8.4 -2018-05-22
CVE-2018-8867 多款GE产品安全漏洞 — GE PACSystems RX3i CPE305/310 version 9.20 and prior RX3i CPE330 version 9.21 and prior RX3i CPE 400 version 9.30 and prior PACSystems RSTi-EP CPE 100 all versionsPACSystems CPU320/CRU320 RXi all versions 7.5 -2018-05-18
CVE-2018-0279 Cisco Enterprise NFV Infrastructure Software Secure Copy Protocol服务器输入验证错误漏洞 — Cisco Enterprise NFV Infrastructure Software 8.8 -2018-05-17
CVE-2018-0280 Cisco Meeting Server 输入验证漏洞 — Cisco Meeting Server Media Services 7.5 -2018-05-17
CVE-2018-0325 Cisco IP Phone 7800 Series和Cisco IP Phone 8800 Series 输入验证漏洞 — Cisco IP Phone 7800 Series and 8800 Series 7.5 -2018-05-17
CVE-2018-4850 Siemens SIMATIC S7-400和SIMATIC S7-400H 安全漏洞 — SIMATIC S7-400 (incl. F) CPU hardware version 4.0 and below, SIMATIC S7-400 (incl. F) CPU hardware version 5.0, SIMATIC S7-400H CPU hardware version 4.5 and below 7.5 -2018-05-16
CVE-2017-6021 Schneider Electric ClearSCADA 安全漏洞 — ClearSCADA 7.5 -2018-05-14
CVE-2018-8869 Lantech IDS 2102 输入验证漏洞 — IDS 2102 9.8 -2018-05-04
CVE-2018-0234 Cisco Aironet 1810、1830和1850 Series Access Points 输入验证漏洞 — Cisco Aironet 1810, 1830, and 1850 Series Access Points 8.6 -2018-05-02
CVE-2018-0235 Cisco Wireless LAN Controller 输入验证错误漏洞 — Cisco Wireless LAN Controller 7.4 -2018-05-02
CVE-2018-0249 多款Cisco产品输入验证错误漏洞 — Cisco Aironet 1800 Series Access Point 6.5 -2018-05-02
CVE-2018-0253 Cisco Secure Access Control System ACS Report组件输入验证漏洞 — Cisco Secure Access Control System 9.8 -2018-05-02
CVE-2018-0264 Cisco WebEx Business Suite meeting sites、WebEx Meetings sites和WebEx Meetings Server 安全漏洞 — Cisco WebEx Advanced Recording Format file players 9.6 -2018-05-02
CVE-2018-0287 Cisco WebEx Business Suite meeting sites、WebEx Meetings sites和WebEx Meetings Server 输入验证漏洞 — Cisco WebEx Advanced Recording Format Player 8.8 -2018-05-02
CVE-2018-1104 Ansible Tower 安全漏洞 — Ansible Tower 8.8 -2018-05-02
CVE-2018-6589 CA Spectrum 安全漏洞 — CA Spectrum 7.5 -2018-05-01
CVE-2018-1102 Red Hat Openshift Enterprise 安全漏洞 — atomic-openshift 8.8 -2018-04-30
CVE-2018-4832 Siemens多款产品输入验证错误漏洞 — OpenPCS 7 V7.1 and earlier 6.5 -2018-04-24

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