CAPEC-108: Command Line Execution through SQL Injection

Command Line Execution through SQL Injection


Typical_Severify: Very High



An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.


ChildOf: CAPEC-66 |SQL Injection

Execution Flow Attack Setp

Setp 1 Explore

[Probe for SQL Injection vulnerability] The attacker injects SQL syntax into user-controllable data inputs to search unfiltered execution of the SQL syntax in a query.

Setp 2 Exploit

[Achieve arbitrary command execution through SQL Injection with the MSSQL_xp_cmdshell directive] The attacker leverages a SQL Injection attack to inject shell code to be executed by leveraging the xp_cmdshell directive.

Setp 3 Exploit

[Inject malicious data in the database] Leverage SQL injection to inject data in the database that could later be used to achieve command injection if ever used as a command line argument

Setp 4 Exploit

[Trigger command line execution with injected arguments] The attacker causes execution of command line functionality which leverages previously injected database content as arguments.


The application does not properly validate data before storing in the database

Backend application implicitly trusts the data stored in the database

Malicious data is used on the backend as a command line argument


Level High

The attacker most likely has to be familiar with the internal functionality of the system to launch this attack. Without that knowledge, there are not many feedback mechanisms to give an attacker the indication of how to perform command injection or whether the attack is succeeding.


None: No specialized resources are required to execute this type of attack.


Scope Impact Likelihood
I n t e g r i t y Modify Data
C o n f i d e n t i a l i t y Read Data
A v a i l a b i l i t y Unreliable Execution
Confidentiality Access Control Authorization Gain Privileges
Confidentiality Integrity Availability Execute Unauthorized Commands


Disable MSSQL xp_cmdshell directive on the database

Properly validate the data (syntactically and semantically) before writing it to the database.

Do not implicitly trust the data stored in the database. Re-validate it prior to usage to make sure that it is safe to use in a given context (e.g. as a command line argument).


SQL injection vulnerability in Cacti 0.8.6i and earlier, when register_argc_argv is enabled, allows remote attackers to execute arbitrary SQL commands via the (1) second or (2) third arguments to cmd.php. NOTE: this issue can be leveraged to execute arbitrary commands since the SQL query results are later used in the polling_items array and popen function (CVE-2006-6799).



89 | SQL命令中使用的特殊元素转义处理不恰当(SQL注入)

74 | 输出中的特殊元素转义处理不恰当(注入)

20 | 输入验证不恰当

78 | OS命令中使用的特殊元素转义处理不恰当(OS命令注入)

114 | 流程控制



2014-06-23 | CAPEC Content Team | The MITRE Corporation


2017-08-04 | CAPEC Content Team | The MITRE Corporation

Updated Resources_Required