Difference between revisions of "Argument Injection or Modification"

From OWASP
Jump to: navigation, search
(Reverting to last version not containing links to www.textdronacelliba.com)
(27 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
{{Template:Attack}}
 
{{Template:Attack}}
 +
<br>
 +
[[Category:OWASP ASDR Project]]
 +
 +
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
 
==Description==
 
==Description==
Argument Injection or Modification is a specific case of attack, which belongs to Injection attacks familly. Modifying or injecting data as arguments the attacker may lead to very simmilar, often the same results as in other injection attacks. It plays no difference if the attacker wants to inject the system command into argument or into any other part of the code.
+
 
 +
Argument Injection or Modification is a type of Injection attack. Modifying or injecting data as an argument may lead to very similar, often the same, results as in other injection attacks. It makes no difference if the attacker wants to inject the system command into arguments or into any other part of the code.
 +
 
 +
==Risk Factors==
 +
TBD
  
 
==Examples ==
 
==Examples ==
  
 +
===Example 1===
  
'''Example 1'''
+
Knowing pseudo code of the application, the attacker may guess what action is required by the application to perform another one, for example, what must be done to authorize the attacker as the administrator.
 
+
Knowing pseudo code of the application the attacker may guess, what action is required by the application to perform another one. E.g. what must be done to authorize the attacker as the administrator.
+
  
 
Reading the code below the attacker doesn't know the values of $pass and $login. The question is - is there possiblity of altering value of $authorized not knowing previously mentioned variables?
 
Reading the code below the attacker doesn't know the values of $pass and $login. The question is - is there possiblity of altering value of $authorized not knowing previously mentioned variables?
Line 26: Line 34:
 
</pre>
 
</pre>
  
 +
===Example 2===
  
'''Example 2'''
+
If the security mechanism doesn't protect data as it should, e.g. doesn't check the identity of the user, and private data are displayed (despite that they shouldn't), then the user may try to alter arguments and get access to data owned by a different user.
  
If security mechanism doesn't protect data as it should, e.g. doesn't check the identity of the user and private data are displayed to him despite of fact they shouldn't, then such user may try to alter arguments and get access to data owned by a different user.
+
For example, by entering the address http://testsite.com/index.php?invoice=12 a user is able to check one of his invoices. Modifying the "invoice" argument, considering the above assumptions, the attacker may try to access other user's invoices. This might be useful to the attacker in a [[Brute force attack]].
  
E.g. By entering address http://testsite.com/index.php?invoice=12 user is able to check one of his invoices. Modifying "invoice" argument, considering above assumptions, the attacker may try to access other user's invoices. Usefull to the attacker in this example would be performing a brute-force attack.
+
==Related [[Threat Agents]]==
 +
TBD
  
 +
==Related [[Attacks]]==
 +
* [[Command Injection]]
 +
* [[Code Injection]]
 +
* [[SQL Injection]]
 +
* [[LDAP injection]]
 +
* [[Server-Side_Includes_%28SSI%29_Injection|Sever-Side Includes (SSI) Injection]]
 +
* [[Cross-site Scripting (XSS)]]
  
==Related Threats==
+
==Related [[Vulnerabilities]]==
 +
* [[:Category:Input Validation Vulnerability]]
  
[[Category:Command Execution]]
+
==Related [[Controls]]==
 +
* [[Input Validation]]
 +
* [[Output Validation]]
 +
* [[Canonicalization]]
  
==Related Attacks==
+
==References==
 +
TBD
  
*[[Command Injection]]
 
*[[Code Injection]]
 
*[[SQL Injection]]
 
*[[LDAP Injection]]
 
*[[SSI Injection]]
 
*[[XSS]]
 
 
==Related Vulnerabilities==
 
 
[[Category: Input Validation Vulnerability]]
 
 
==Related Countermeasures==
 
 
- validation of the format / expected classes of charachetrs / input/output data size
 
 
==Categories==
 
  
 
[[Category: Injection]]
 
[[Category: Injection]]
 
+
[[Category: Attack]]
[[Category:Attack]]
+

Revision as of 13:29, 27 May 2009

This is an Attack. To view all attacks, please see the Attack Category page.




Last revision (mm/dd/yy): 05/27/2009

Description

Argument Injection or Modification is a type of Injection attack. Modifying or injecting data as an argument may lead to very similar, often the same, results as in other injection attacks. It makes no difference if the attacker wants to inject the system command into arguments or into any other part of the code.

Risk Factors

TBD

Examples

Example 1

Knowing pseudo code of the application, the attacker may guess what action is required by the application to perform another one, for example, what must be done to authorize the attacker as the administrator.

Reading the code below the attacker doesn't know the values of $pass and $login. The question is - is there possiblity of altering value of $authorized not knowing previously mentioned variables?

$authorized=0;

if($pass = "XXX" and $login = "XXX") { $authorized = 1; }
if($authorized == 1) { admin_panel(); }

If server configuration allows for that, we may try to pass argument $authorized=1 as input data to application.

E.g. /index.php?user=&pass=&authorized=1

Example 2

If the security mechanism doesn't protect data as it should, e.g. doesn't check the identity of the user, and private data are displayed (despite that they shouldn't), then the user may try to alter arguments and get access to data owned by a different user.

For example, by entering the address http://testsite.com/index.php?invoice=12 a user is able to check one of his invoices. Modifying the "invoice" argument, considering the above assumptions, the attacker may try to access other user's invoices. This might be useful to the attacker in a Brute force attack.

Related Threat Agents

TBD

Related Attacks

Related Vulnerabilities

Related Controls

References

TBD