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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

1335 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 ControlBypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access ControlGain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity, Confidentiality, AvailabilityExecute 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-RepudiationHide Activities
Often the actions performed by injected control code are unlogged.
Mitigations (5)
Architecture and DesignRefactor your program so that you do not have to dynamically generate code.
Architecture and DesignRun 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…
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…
TestingUse 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.
OperationRun 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 IDTitleCVSSSeverityPublished
CVE-2021-45029 Apache ShenYu 2.4.1 Groovy Code Injection & SpEL Injection — Apache ShenYu (incubating) 9.8 -2022-01-25
CVE-2021-23154 Command injection in Lens causes arbitrary shell command execution when malicious custom helm chart configuration provided — Lens 6.3 Medium2022-01-10
CVE-2022-22286 Samsung Bixby Routines App 代码注入漏洞 — Bixby Routines 4.4 Medium2022-01-07
CVE-2022-22285 Samsung Reminder App 代码注入漏洞 — Reminder 4.4 Medium2022-01-07
CVE-2022-22270 Samsung SMR 安全漏洞 — Samsung Mobile Devices 4.4 Medium2022-01-07
CVE-2021-23814 laravel-filemanager代码问题漏洞 — unisharp/laravel-filemanager 6.7 Medium2021-12-17
CVE-2021-43811 Code injection via unsafe YAML loading — sockeye 7.8 High2021-12-08
CVE-2021-44529 Ivanti Endpoint Manager 代码注入漏洞 — Ivanti EPM 9.8 -2021-12-08
CVE-2021-38448 Trane Symbio Improper Control of Generation of Code — Symbio 7.5 High2021-11-22
CVE-2021-22053 VMware Spring Cloud Netflix 代码注入漏洞 — Spring Cloud Netflix 8.8 -2021-11-19
CVE-2021-41269 Unauthenticated remote code injection in cron-utils — cron-utils 10.0 Critical2021-11-15
CVE-2021-24721 Loco Translate < 2.5.4 - Authenticated PHP Code Injection — Loco Translate 6.5 -2021-11-08
CVE-2021-24537 Similar Posts <= 3.1.5 - Admin+ Arbitrary PHP Code Execution — Similar Posts – Best Related Posts Plugin for WordPress 7.2 -2021-11-08
CVE-2021-38450 Trane Tracer Code Injection — Tracer SC 9.9 Critical2021-10-27
CVE-2021-22961 GlassWire 代码注入漏洞 — GlassWire 9.8 -2021-10-18
CVE-2021-24546 EditorsKit < 1.31.6 - Contributor+ Arbitrary PHP Code Execution — Gutenberg Block Editor Toolkit – EditorsKit 8.8 -2021-10-11
CVE-2021-25470 Samsung SMR 安全漏洞 — Samsung Mobile Devices 7.9 High2021-10-06
CVE-2021-22557 Code execution in SLO Generator via YAML Payload — SLO Generator 5.3 Medium2021-10-04
CVE-2021-22952 UniFi Talk 代码注入漏洞 — UniFi Talk application 8.8 -2021-09-23
CVE-2021-33693 SAP ERP 代码注入漏洞 — SAP Cloud Connector 7.2 -2021-09-15
CVE-2021-32836 Pre-auth unsafe deserialization in ZStack — zstack 7.5 High2021-09-09
CVE-2021-32834 Arbitrary Groovy script evaluation in Eclipse Keti — keti 8.2 High2021-09-09
CVE-2021-32831 Code injection in total.js — framework 7.5 High2021-08-30
CVE-2021-39159 Remote code execution in Binderhub — binderhub 9.6 Critical2021-08-25
CVE-2021-39160 Code injection in nbgitpuller — nbgitpuller 9.6 Critical2021-08-25
CVE-2021-39144 XStream is vulnerable to a Remote Command Execution attack — xstream 8.5 High2021-08-23
CVE-2021-3615 Lenovo Smart Camera 代码注入漏洞 — Smart Camera X3, X5, and C2E firmware 6.6 Medium2021-08-17
CVE-2021-32829 Post-authentication Remote Code Execution (RCE) in ZStack REST API — zstack 9.6 Critical2021-08-17
CVE-2021-32809 Arbitrary HTML injection vulnerability in ckeditor — ckeditor4 4.6 Medium2021-08-12
CVE-2021-37626 PHP file inclusion via insert tags — contao 7.2 High2021-08-11

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