CAPEC-88: OS Command Injection |
 Description In this type of an attack, an adversary injects operating system commands into existing application functions. An application that uses untrusted input to build command strings is vulnerable. An adversary can leverage OS command injection in an application to elevate privileges, execute arbitrary commands and compromise the underlying operating system. Likelihood Of Attack Typical Severity Execution Flow Explore Identify inputs for OS commands: The attacker determines user controllable input that gets passed as part of a command to the underlying operating system. | Techniques |
|---|
| Port mapping. Identify ports that the system is listening on, and attempt to identify inputs and protocol types on those ports. | | TCP/IP Fingerprinting. The attacker uses various software to make connections or partial connections and observe idiosyncratic responses from the operating system. Using those responses, they attempt to guess the actual operating system. | | Induce errors to find informative error messages |
Survey the Application: The attacker surveys the target application, possibly as a valid and authenticated user | Techniques |
|---|
| Spidering web sites for all available links | | Inventory all application inputs |
Experiment Vary inputs, looking for malicious results.: Depending on whether the application being exploited is a remote or local one the attacker crafts the appropriate malicious input, containing OS commands, to be passed to the application | Techniques |
|---|
| Inject command delimiters using network packet injection tools (netcat, nemesis, etc.) | | Inject command delimiters using web test frameworks (proxies, TamperData, custom programs, etc.) |
Exploit Execute malicious commands: The attacker may steal information, install a back door access mechanism, elevate privileges or compromise the system in some other way. | Techniques |
|---|
| The attacker executes a command that stores sensitive information into a location where they can retrieve it later (perhaps using a different command injection). |
Prerequisites
| User controllable input used as part of commands to the underlying operating system. |
Skills Required
[Level: High] The attacker needs to have knowledge of not only the application to exploit but also the exact nature of commands that pertain to the target operating system. This may involve, though not always, knowledge of specific assembly commands for the platform. |
Consequences  This table specifies different individual consequences associated with the attack pattern. The Scope identifies the security property that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in their attack. The Likelihood provides information about how likely the specific consequence is expected to be seen relative to the other consequences in the list. For example, there may be high likelihood that a pattern will be used to achieve a certain impact, but a low likelihood that it will be exploited to achieve a different impact.| Scope | Impact | Likelihood |
|---|
Confidentiality Integrity Availability | Execute Unauthorized Commands | | Confidentiality Access Control Authorization | Gain Privileges Bypass Protection Mechanism | | Confidentiality | Read Data | |
Mitigations
| Use language APIs rather than relying on passing data to the operating system shell or command line. Doing so ensures that the available protection mechanisms in the language are intact and applicable. |
| Filter all incoming data to escape or remove characters or strings that can be potentially misinterpreted as operating system or shell commands |
| All application processes should be run with the minimal privileges required. Also, processes must shed privileges as soon as they no longer require them. |
Example Instances
A transaction processing system relies on code written in a number of languages. To access this functionality, the system passes transaction information on the system command line. An attacker can gain access to the system command line and execute malicious commands by injecting these commands in the transaction data. If successful, the attacker can steal information, install backdoors and perform other nefarious activities that can compromise the system and its data. See also: A vulnerability in Mozilla Firefox 1.x browser allows an attacker to execute arbitrary commands on the UNIX/Linux operating system. The vulnerability is caused due to the shell script used to launch Firefox parsing shell commands that are enclosed within back-ticks in the URL provided via the command line. This can be exploited to execute arbitrary shell commands by tricking a user into following a malicious link in an external application which uses Firefox as the default browser (e.g. the mail client Evolution on Red Hat Enterprise Linux 4). |
Taxonomy Mappings Relevant to the WASC taxonomy mapping | Entry ID | Entry Name |
|---|
| 31 | OS Commanding |
References  Content History | Submissions |
|---|
| Submission Date | Submitter | Organization |
|---|
| 2014-06-23 (Version 2.6) | CAPEC Content Team | The MITRE Corporation | | | Modifications |
|---|
| Modification Date | Modifier | Organization |
|---|
| 2020-07-30 (Version 3.3) | CAPEC Content Team | The MITRE Corporation | | Updated Execution_Flow | | 2020-12-17 (Version 3.4) | CAPEC Content Team | The MITRE Corporation | | Updated Taxonomy_Mappings | | 2021-06-24 (Version 3.5) | CAPEC Content Team | The MITRE Corporation | | Updated Execution_Flow, Related_Weaknesses |
More information is available — Please select a different filter.
|
