| Name |
Email Injection |
|
| Likelyhood of attack |
Typical severity |
| Low |
Medium |
|
| Summary |
An adversary manipulates the headers and content of an email message by injecting data via the use of delimiter characters native to the protocol. |
| Prerequisites |
The target application must allow the user to send email to some recipient, to specify the content at least one header field in the message, and must fail to sanitize against the injection of command separators. The adversary must have the ability to access the target mail application. |
| Solutions | |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-150 |
Improper Neutralization of Escape, Meta, or Control Sequences |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-137 |
An adversary manipulates the content of request parameters for the purpose of undermining the security of the target. Some parameter encodings use text characters as separators. For example, parameters in a HTTP GET message are encoded as name-value pairs separated by an ampersand (&). If an attacker can supply text strings that are used to fill in these parameters, then they can inject special characters used in the encoding scheme to add or modify parameters. For example, if user input is fed directly into an HTTP GET request and the user provides the value "myInput&new_param=myValue", then the input parameter is set to myInput, but a new parameter (new_param) is also added with a value of myValue. This can significantly change the meaning of the query that is processed by the server. Any encoding scheme where parameters are identified and separated by text characters is potentially vulnerable to this attack - the HTTP GET encoding used above is just one example. |
|
| Taxonomy: WASC |
|
Entry ID
|
Entry Name
|
| 30 |
Mail Command Injection |
|