Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-94 (对生成代码的控制不恰当(代码注入)) — Vulnerability Class 1752

1752 vulnerabilities classified as CWE-94 (对生成代码的控制不恰当(代码注入)). AI Chinese analysis included.

CWE-94 represents a critical code injection weakness where software constructs executable code using untrusted input without proper sanitization. Attackers typically exploit this vulnerability by injecting malicious scripts or commands into user-supplied fields, such as web forms or API parameters, which the application then executes directly. This allows adversaries to bypass security controls, steal sensitive data, or gain unauthorized administrative access to the underlying system. To prevent such exploits, developers must rigorously validate and sanitize all external inputs, ensuring that only expected characters are processed. Implementing strict allow-listing strategies, utilizing parameterized queries for database interactions, and avoiding dynamic code execution functions like eval() are essential defensive measures. By treating all user input as potentially hostile and applying robust encoding techniques, organizations can effectively neutralize injection vectors and maintain application integrity.

MITRE CWE Description
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Common Consequences (4)
Access Control Bypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access Control Gain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity, Confidentiality, Availability Execute Unauthorized Code or Commands
When a product allows a user's input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. As a result, code injection can often result in the execution of arbitrary code. Code injection attacks can…
Non-Repudiation Hide Activities
Often the actions performed by injected control code are unlogged.
Mitigations (5)
Architecture and Design Refactor your program so that you do not have to dynamically generate code.
Architecture and Design Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating s…
Implementation Assume 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…
Testing Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
Operation Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).
Examples (2)
This example attempts to write user messages to a message file and allow users to view them.
$MessageFile = "messages.out"; if ($_GET["action"] == "NewMessage") { $name = $_GET["name"]; $message = $_GET["message"]; $handle = fopen($MessageFile, "a+"); fwrite($handle, "<b>$name</b> says '$message'<hr>\n"); fclose($handle); echo "Message Saved!<p>\n"; } else if ($_GET["action"] == "ViewMessages") { include($MessageFile); }
Bad · PHP
name=h4x0r message=%3C?php%20system(%22/bin/ls%20-l%22);?%3E
Attack
edit-config.pl: This CGI script is used to modify settings in a configuration file.
use CGI qw(:standard); sub config_file_add_key { my ($fname, $key, $arg) = @_; # code to add a field/key to a file goes here } sub config_file_set_key { my ($fname, $key, $arg) = @_; # code to set key to a particular file goes here } sub config_file_delete_key { my ($fname, $key, $arg) = @_; # code to delete key from a particular file goes here } sub handleConfigAction { my ($fname, $action) = @_; my $key = param('key'); my $val = param('val'); # this is super-efficient code, especially if you have to invoke # any one of dozens of different functions! my $code = "config_file_$action_key(\$fnam
Bad · Perl
add_key(",","); system("/bin/ls");
Attack
CVE ID Title CVSS Severity Published
CVE-2020-15252 RCE in XWiki — xwiki-platform 8.5 High 2020-10-16
CVE-2020-8243 Pulse Secure Pulse Connect Secure 代码注入漏洞 — Pulse Connect Secre 7.2 - 2020-09-29
CVE-2020-15171 Users with SCRIPT rights can execute arbitrary code in XWiki — xwiki-platform 6.6 Medium 2020-09-10
CVE-2020-7381 Code Injection in Rapid7 Nexpose Installer — Nexpose 5.8 Medium 2020-09-03
CVE-2020-15167 Arbitrary code execution via configuration file in Miller — miller 8.2 High 2020-09-02
CVE-2020-15150 Remote Code Execution in paginator(hex) — paginator 9.0 Critical 2020-09-01
CVE-2020-15147 Remote Code Execution in Red Discord Bot — Red-DiscordBot 8.5 High 2020-08-21
CVE-2020-15142 Arbitrary Code Generation — openapi-python-client 8.0 High 2020-08-14
CVE-2020-10055 Siemens Desigo CC和Desigo CC Compact 代码注入漏洞 — Desigo CC 8.1 - 2020-08-14
CVE-2020-8224 Nextcloud Desktop Client 代码注入漏洞 — Desktop Client 7.8 - 2020-08-10
CVE-2020-8218 Pulse Secure Pulse Connect Secure 代码注入漏洞 — Pulse Connect Secure 7.2 - 2020-07-30
CVE-2020-12013 Mitsubishi Electric MC Works32 SQL注入漏洞 — MC Works64 9.8 - 2020-07-16
CVE-2020-8194 Citrix Systems Citrix Application Delivery Controller、Citrix Gateway和Citrix SDWAN WAN-OP 代码注入漏洞 — Citrix ADC, Citrix Gateway, Citrix SDWAN WAN-OP 8.1 - 2020-07-10
CVE-2020-8163 Ruby on Rails 代码注入漏洞 — https://github.com/rails/rails 8.8 - 2020-07-02
CVE-2020-8180 Nextcloud Talk 代码注入漏洞 — Nextcloud Talk 9.9 - 2020-06-08
CVE-2020-7013 Elasticsearch Kibana 代码注入漏洞 — Kibana 8.8 - 2020-06-03
CVE-2020-7012 Elasticsearch Kibana 代码注入漏洞 — Kibana 8.8 - 2020-06-03
CVE-2020-11079 command injection fix in node-dns-sync — node-dns-sync 8.6 High 2020-05-28
CVE-2020-8149 logkitty npm package 代码注入漏洞 — logkitty 9.8 - 2020-05-15
CVE-2020-11057 Code Injection in XWiki Platform — XWiki Platform 9.9 Critical 2020-05-12
CVE-2020-11056 Potential Code Injection in Sprout Forms — Sprout Forms 7.4 High 2020-05-07
CVE-2020-5739 Grandstream GXP1600 代码注入漏洞 — Grandstream GXP1600 Series 8.8 - 2020-04-14
CVE-2020-10684 Ansible Engine 代码注入漏洞 — Ansible 7.9 High 2020-03-24
CVE-2020-7480 Schneider Electric Andover Continuum 代码注入漏洞 — Andover Continuum (All versions) 9.8 - 2020-03-23
CVE-2020-8140 Nextcloud Desktop Client 代码注入漏洞 — Desktop Client 6.7 - 2020-03-20
CVE-2020-8137 blamer 代码注入漏洞 — blamer 9.8 - 2020-03-20
CVE-2019-18582 Dell EMC Data Protection Advisor 代码注入漏洞 — Data Protection Advisor 7.2 - 2020-03-18
CVE-2020-8141 dot package 代码注入漏洞 — dot 8.8 - 2020-03-15
CVE-2020-5258 Prototype pollution in dojo — dojo 7.7 High 2020-03-10
CVE-2020-5259 Prototype Pollution in Dojox — dojox 7.7 High 2020-03-10

Vulnerabilities classified as CWE-94 (对生成代码的控制不恰当(代码注入)) represent 1752 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.