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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

2063 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-2021-27446 Weintek EasyWeb cMT Code Injection — cMT-SVR-1xx/2xx 10.0 Critical 2022-05-16
CVE-2022-0578 Code Injection in publify/publify — publify/publify 5.3 - 2022-05-16
CVE-2022-24817 Improper kubeconfig validation allows arbitrary code execution — flux2 9.9 Critical 2022-05-06
CVE-2022-1575 Arbitrary Code Execution through Sanitizer Bypass in jgraph/drawio — jgraph/drawio 9.6 - 2022-05-05
CVE-2022-29821 Jetbrains Rider 代码注入漏洞 — Rider 6.9 Medium 2022-04-28
CVE-2022-29819 Jetbrains JetBrains IntelliJ IDEA 代码注入漏洞 — IntelliJ IDEA 6.9 Medium 2022-04-28
CVE-2022-29815 Jetbrains JetBrains IntelliJ IDEA 代码注入漏洞 — IntelliJ IDEA 6.9 Medium 2022-04-28
CVE-2022-29814 Jetbrains IntelliJ IDEA 代码注入漏洞 — IntelliJ IDEA 6.9 Medium 2022-04-28
CVE-2022-29813 JetBrains IntelliJ IDEA 代码注入漏洞 — IntelliJ IDEA 6.9 Medium 2022-04-28
CVE-2022-24735 Lua scripts can be manipulated to overcome ACL rules in Redis — redis 3.9 Low 2022-04-27
CVE-2022-24881 Command Injection in Ballcat Codegen — ballcat-codegen 8.8 High 2022-04-26
CVE-2022-0661 Ad Injection <= 1.2.0.19 - Admin+ Stored Cross-Site Scripting & RCE — Ad Injection 7.2 - 2022-04-18
CVE-2022-24816 Improper Control of Generation of Code in jai-ext — jai-ext 10.0 Critical 2022-04-13
CVE-2022-27837 Samsung Accessibility安全漏洞 — Accessibility 4.4 Medium 2022-04-11
CVE-2022-24780 Code Injection in Combodo iTop — iTop 8.8 High 2022-04-05
CVE-2022-1159 Rockwell Automation Studio 5000 Logix Designer Code Injection — Studio 5000 Logix Designer 7.7 High 2022-04-01
CVE-2022-22965 Spring Framework 代码注入漏洞 — Spring Framework 9.8 - 2022-04-01
CVE-2022-22963 Spring Framework 代码注入漏洞 — Spring Cloud Function 9.8 - 2022-04-01
CVE-2020-25197 GE Reason RT43X Clocks Code Injection — Reason RT43X Clocks 9.8 Critical 2022-03-18
CVE-2022-0811 cri-o 代码注入漏洞 — CRI-O 8.8 - 2022-03-16
CVE-2021-25003 WPCargo < 6.9.0 - Unauthenticated RCE — WPCargo Track & Trace 9.8 - 2022-03-14
CVE-2022-0921 Abusing Backup/Restore feature to achieve Remote Code Execution in microweber/microweber — microweber/microweber 7.2 - 2022-03-11
CVE-2022-24734 Remote code execution in mybb — mybb 7.2 High 2022-03-09
CVE-2022-24915 ICSA-22-062-01 IPCOMM ipDIO — IPCOMM ipDIO 8.0 High 2022-03-09
CVE-2022-22985 ICSA-22-062-01 IPCOMM ipDIO — IPCOMM ipDIO 8.8 High 2022-03-09
CVE-2022-0845 Code Injection in pytorchlightning/pytorch-lightning — pytorchlightning/pytorch-lightning 8.8 - 2022-03-05
CVE-2022-22947 VMware Spring Cloud Gateway 代码注入漏洞 — Spring Cloud Gateway 10.0 - 2022-03-03
CVE-2022-0819 Code Injection in dolibarr/dolibarr — dolibarr/dolibarr 8.1 - 2022-03-02
CVE-2022-23642 Code Injection in Sourcegraph — sourcegraph 8.8 High 2022-02-18
CVE-2022-24663 Remote Code Execution by Subscriber+ users via WordPress shortcode — PHP Everywhere 9.9 Critical 2022-02-16

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