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 3319

3319 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-2017-12277 Cisco Firepower 4100 Series Next-Generation Firewall和Cisco Firepower 9300 Security Appliance 命令注入漏洞 — Cisco Firepower 4100 Series NGFW and Firepower 9300 Security Appliance 8.8 -2017-11-02
CVE-2017-12285 Cisco Network Analysis Module Software 路径遍历漏洞 — Cisco Network Analysis Module 5.3 -2017-10-19
CVE-2017-12286 Cisco Jabber 信息泄露漏洞 — Cisco Jabber 5.5 -2017-10-19
CVE-2017-12301 多款Cisco产品NX-OS Software Python scripting子系统安全漏洞 — Cisco NX-OS Software 6.3 -2017-10-19
CVE-2017-1002153 Koji 安全漏洞 — Koji 7.5 -2017-10-06
CVE-2017-12244 多款Cisco产品Firepower System Software 安全漏洞 — Cisco Firepower Detection Engine 7.5 -2017-10-05
CVE-2017-12264 Cisco Meeting Server Web Admin Interface 安全漏洞 — Cisco Meeting Server 5.3 -2017-10-05
CVE-2017-12228 Cisco IOS和IOS XE Network Plug and Play应用程序信息泄露漏洞 — Cisco IOS and IOS XE 7.4 -2017-09-28
CVE-2017-12233 Cisco IOS 输入验证漏洞 — Cisco IOS 7.5 -2017-09-28
CVE-2017-12234 Cisco IOS 输入验证漏洞 — Cisco IOS 7.5 -2017-09-28
CVE-2017-12235 Cisco IOS 输入验证漏洞 — Cisco IOS 7.5 -2017-09-28
CVE-2017-12240 Cisco IOS和IOS XE Software DHCP relay子系统缓冲区错误漏洞 — Cisco IOS and IOS XE 9.8 -2017-09-28
CVE-2017-12215 Cisco Email Security Appliance AsyncOS Software 安全漏洞 — Cisco Email Security Appliance 8.6 -2017-09-21
CVE-2017-12252 Cisco FindIT Network Discovery Utility 安全漏洞 — Cisco FindIT 7.8 -2017-09-21
CVE-2017-12255 Cisco UCS Central Software 安全漏洞 — Cisco UCS Central Software 7.8 -2017-09-21
CVE-2017-7924 多款Rockwell Automation产品输入验证漏洞 — Rockwell Automation MicroLogix 1100 Controllers 7.5 -2017-09-20
CVE-2017-12217 Cisco ASR 5500 System Architecture Evolution Gateways 安全漏洞 — Cisco ASR 5500 System Architecture Evolution Gateway 5.3 -2017-09-07
CVE-2017-12218 Cisco Email Security Appliances Advanced Malware Protection 安全漏洞 — Cisco Email Security Appliance 5.8 -2017-09-07
CVE-2017-12223 Cisco IR800 Integrated Services Router Software 输入验证漏洞 — Cisco IR800 Integrated Services Router 6.4 -2017-09-07
CVE-2017-6792 Cisco Prime Collaboration Provisioning Tool 安全漏洞 — Cisco Prime Collaboration Provisioning Tool 6.5 -2017-09-07
CVE-2017-6794 Cisco Meeting Server 安全漏洞 — Cisco Meeting Server 6.7 -2017-09-07
CVE-2017-6795 Cisco ASR 920 Series Aggregation Services Routers IOS XE Software 安全漏洞 — Cisco IOS XE 4.4 -2017-09-07
CVE-2017-6759 Cisco Prime Collaboration Provisioning Tool UpgradeManager 输入验证漏洞 — Cisco Prime Collaboration Provisioning Tool 6.5 -2017-08-07
CVE-2017-6763 Cisco Meeting Server 安全漏洞 — Cisco Meeting Server 7.5 -2017-08-07
CVE-2017-6770 多款Cisco产品OSPF LSA Manipulation 输入验证错误漏洞 — Multiple Cisco Products 4.8 -2017-08-07
CVE-2017-7522 OpenVPN 安全漏洞 — OpenVPN 6.5 -2017-06-27
CVE-2017-6662 Cisco Prime Infrastructure和Evolved Programmable Network Manager 安全漏洞 — Cisco Prime Infrastructure and Evolved Programmable Network Manager 8.0 -2017-06-26
CVE-2017-6649 Cisco Nexus 5000 Series Switches NX-OS System Software 命令注入漏洞 — Cisco Nexus Series Switches 7.8 -2017-05-22
CVE-2017-6650 Cisco Nexus 5000 Series Switches NX-OS System Software 命令注入漏洞 — Cisco Nexus Series Switches 6.7 -2017-05-22
CVE-2017-3825 多款Cisco产品TelePresence Collaboration Endpoint Software 安全漏洞 — Cisco TelePresence 7.5 -2017-05-16

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