CWE-77
Improper Neutralization of Special Elements used in a Command ('Command Injection')
AI Translation Available
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Status
draft
Abstraction
class
Likelihood
high
Affected Platforms
AI/ML
Extended Description
AI Translation
Many protocols and products have their own custom command language. While OS or shell command strings are frequently discovered and targeted, developers may not realize that these other command languages might also be vulnerable to attacks.
Technical Details
AI Translation
Common Consequences
integrity
confidentiality
availability
Impacts
execute unauthorized code or commands
Detection Methods
automated static analysis
Potential Mitigations
Phases:
architecture and design
implementation
operation
system configuration
Descriptions:
•
If possible, ensure that all external commands called from the program are statically created.
•
Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
•
If at all possible, use library calls rather than external processes to recreate the desired functionality.
•
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 of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
•
Assign permissions that prevent the user from accessing/opening privileged files.