Difference between revisions of "Injection problem"

From OWASP
Jump to: navigation, search
(Related problems)
Line 1: Line 1:
 
{{Template:SecureSoftware}}
 
{{Template:SecureSoftware}}
  
==Overview==
+
{{Template:Vulnerability}}
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 +
 
 +
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 +
 
 +
[[ASDR Table of Contents]]
 +
__TOC__
 +
 
 +
 
 +
==Description==
  
 
Injection problems span a wide range of instantiations. The basic form of this flaw involves the injection of control-plane data into the data-plane in order to alter the control flow of the process.
 
Injection problems span a wide range of instantiations. The basic form of this flaw involves the injection of control-plane data into the data-plane in order to alter the control flow of the process.
  
==Consequences ==
+
'''Consequences'''
 +
 
 +
* Confidentiality: Many injection attacks involve the disclosure of important information - in terms of both data sensitivity and usefulness in further exploitation
 +
* Authentication: In some cases injectable code controls authentication; this may lead to remote vulnerability
 +
* Access Control: Injection attacks are characterized by the ability to significantly change the flow of a given process, and in some cases, to the execution of arbitrary code.
 +
* Integrity: Data injection attacks lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing.
 +
* Accountability: Often the actions performed by injected control code are unlogged.
 +
 
 +
'''Exposure period'''
 +
 
 +
* Requirements specification: A language might be chosen which is not subject to these issues.
 +
* Implementation: Many logic errors can contribute to these issues.
 +
 
 +
'''Platform'''
 +
 
 +
* Languages: C, C++, Assembly, SQL
 +
* Platforms: Any
 +
 
 +
'''Required resources'''
 +
 
 +
Any
 +
 
 +
'''Severity'''
 +
 
 +
High
 +
 
 +
'''Likelihood of exploit'''
 +
 
 +
Very High
 +
 
 +
Injection problems encompass a wide variety of issues - all mitigated in very different ways. For this reason, the most effective way to discuss these flaws is to note the distinct features which classify them as injection flaws.
 +
 
 +
The most important issue to note is that all injection problems share one thing in common - i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed.
 +
 
 +
The most classing instantiations of this category of flaw are SQL injection and format string vulnerabilities.
 +
 
 +
 
 +
==Risk Factors==
 +
 
 +
TBD
 +
 
 +
==Examples==
 +
 
 +
===Short example name===
 +
: A short example description, small picture, or sample code with [http://www.site.com links]
 +
 
 +
===Short example name===
 +
: A short example description, small picture, or sample code with [http://www.site.com links]
 +
 
 +
 
 +
==Related [[Attacks]]==
 +
 
 +
* [[Attack 1]]
 +
* [[Attack 2]]
 +
 
 +
 
 +
==Related [[Vulnerabilities]]==
 +
 
 +
* [[Vulnerability 1]]
 +
* [[Vulnerabiltiy 2]]
 +
 
 +
 
 +
==Related [[Controls]]==
 +
 
 +
* Requirements specification: A language might be chosen which is not subject to these issues.
 +
* Implementation: As so many possible implementations of this flaw exist, it is best to simply be aware of the flaw and work to ensure that all control characters entered in data are subject to black-list style parsing.
 +
 
 +
 
 +
==Related [[Technical Impacts]]==
 +
 
 +
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
 +
 
 +
 
 +
==References==
  
* Confidentiality: Many injection attacks involve the disclosure of important information - in terms of both data sensitivity and usefulness in further exploitation
+
TBD
  
* Authentication: In some cases injectable code controls authentication; this may lead to remote vulnerability
+
[[Category:FIXME|add links
  
* Access Control: Injection attacks are characterized by the ability to significantly change the flow of a given process, and in some cases, to the execution of arbitrary code.
+
In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>
  
* Integrity: Data injection attacks lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing.
+
Availability Vulnerability
  
* Accountability: Often the actions performed by injected control code are unlogged.
+
Authorization Vulnerability
  
==Exposure period ==
+
Authentication Vulnerability
  
* Requirements specification: A language might be chosen which is not subject to these issues.
+
Concurrency Vulnerability
  
* Implementation: Many logic errors can contribute to these issues.
+
Configuration Vulnerability
  
==Platform ==
+
Cryptographic Vulnerability
  
* Languages: C, C++, Assembly, SQL
+
Encoding Vulnerability
  
* Platforms: Any
+
Error Handling Vulnerability
  
==Required resources ==
+
Input Validation Vulnerability
  
Any
+
Logging and Auditing Vulnerability
  
==Severity ==
+
Session Management Vulnerability]]
  
High
+
__NOTOC__
  
==Likelihood  of exploit ==
 
  
Very High
+
[[Category:OWASP ASDR Project]]
  
==Avoidance and mitigation ==
 
  
* Requirements specification: A language might be chosen which is not subject to these issues.
+
==Overview==
  
* Implementation: As so many possible implementations of this flaw exist, it is best to simply be aware of the flaw and work to ensure that all control characters entered in data are subject to black-list style parsing.
 
  
==Discussion ==
+
==Avoidance and mitigation ==
  
Injection problems encompass a wide variety of issues - all mitigated in very different ways. For this reason, the most effective way to discuss these flaws is to note the distinct features which classify them as injection flaws.
 
  
The most important issue to note is that all injection problems share one thing in common - i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed.
+
==Discussion ==
  
The most classing instantiations of this category of flaw are SQL injection and format string vulnerabilities.
 
  
 
==Examples ==
 
==Examples ==

Revision as of 09:04, 26 September 2008


This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.

Last revision (mm/dd/yy): 09/26/2008

Vulnerabilities Table of Contents

ASDR Table of Contents


Description

Injection problems span a wide range of instantiations. The basic form of this flaw involves the injection of control-plane data into the data-plane in order to alter the control flow of the process.

Consequences

  • Confidentiality: Many injection attacks involve the disclosure of important information - in terms of both data sensitivity and usefulness in further exploitation
  • Authentication: In some cases injectable code controls authentication; this may lead to remote vulnerability
  • Access Control: Injection attacks are characterized by the ability to significantly change the flow of a given process, and in some cases, to the execution of arbitrary code.
  • Integrity: Data injection attacks lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing.
  • Accountability: Often the actions performed by injected control code are unlogged.

Exposure period

  • Requirements specification: A language might be chosen which is not subject to these issues.
  • Implementation: Many logic errors can contribute to these issues.

Platform

  • Languages: C, C++, Assembly, SQL
  • Platforms: Any

Required resources

Any

Severity

High

Likelihood of exploit

Very High

Injection problems encompass a wide variety of issues - all mitigated in very different ways. For this reason, the most effective way to discuss these flaws is to note the distinct features which classify them as injection flaws.

The most important issue to note is that all injection problems share one thing in common - i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed.

The most classing instantiations of this category of flaw are SQL injection and format string vulnerabilities.


Risk Factors

TBD

Examples

Short example name

A short example description, small picture, or sample code with links

Short example name

A short example description, small picture, or sample code with links


Related Attacks


Related Vulnerabilities


Related Controls

  • Requirements specification: A language might be chosen which is not subject to these issues.
  • Implementation: As so many possible implementations of this flaw exist, it is best to simply be aware of the flaw and work to ensure that all control characters entered in data are subject to black-list style parsing.


Related Technical Impacts


References

TBD


Overview

Avoidance and mitigation

Discussion

Examples

Injection problems describe a large subset of problems with varied instantiations. For an example of one of these problems, see the section Format string problem.

Related problems