Difference between revisions of "Unchecked array indexing"

From OWASP
Jump to: navigation, search
(Related problems)
(Reverting to last version not containing links to s1.shard.jp)
 
(14 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 +
{{Template:Vulnerability}}
 +
{{Template:SecureSoftware}}
  
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
{{Template:SecureSoftware}}
+
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
  
==Overview==
+
==Description==
  
 
Unchecked array indexing occurs when an unchecked value is used as an index into a buffer.
 
Unchecked array indexing occurs when an unchecked value is used as an index into a buffer.
  
==Consequences ==
+
'''Consequences'''
  
* Availability: Unchecked array indexing will very likely result in the corruption of relevant memory and perhaps instructions, leading to a crash, if the values are outside of the valid memory area
+
* Availability: Unchecked array indexing will very likely result in the corruption of relevant memory and perhaps instructions, leading to a crash, if the values are outside of the valid memory area
 +
* Integrity: If the memory corrupted is data, rather than instructions, the system will continue to function with improper values.
 +
* Access Control: If the memory corrupted memory can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow.
  
* Integrity: If the memory corrupted is data, rather than instructions, the system will continue to function with improper values.
+
'''Exposure period'''
  
* Access Control: If the memory corrupted memory can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow.
+
* Requirements specification: The choice could be made to use a language that is not susceptible to these issues.
 +
* Implementation: Many logic errors can lead to this condition. It can be exacerbated by lack of or misuse of mitigating technologies.
  
==Exposure period ==
+
'''Platform'''
  
* Requirements specification: The choice could be made to use a language that is not susceptible to these issues.
+
* Languages: C, C++, Assembly
 +
* Operating Platforms: All
  
* Implementation: Many logic errors can lead to this condition. It can be exacerbated by lack of or misuse of mitigating technologies.
+
'''Required resources'''
  
==Platform ==
+
Any
  
* Languages: C, C++, Assembly
+
'''Severity'''
  
* Operating Platforms: All
+
Medium
  
==Required resources ==
+
'''Likelihood of exploit'''
  
Any
+
Medium
  
==Severity ==
+
Unchecked array indexing, depending on its instantiation, can be responsible for any number of related issues. Most prominent of these possible flaws is the buffer overflow condition. Due to this fact, consequences range from denial of service, and data corruption, to full blown arbitrary code execution
  
Medium
+
The most common condition situation leading to unchecked array indexing is the use of loop index variables as buffer indexes. If the end condition for the loop is subject to a flaw, the index can grow or shrink unbounded, therefore causing a buffer overflow or underflow.  Another common situation leading to this condition is the use of a function's return value, or the resulting value of a calculation directly as an index in to a buffer.
  
==Likelihood  of exploit ==
 
  
Medium
+
==Risk Factors==
  
==Avoidance and mitigation ==
+
TBD
  
* Requirements specification: The choice could be made to use a language that is not susceptible to these issues.
+
==Examples==
  
* Implementation: Include sanity checks to ensure the validity of any values used as index variables. In loops, use greater-than-or-equal-to, or less-than-or-equal-to, as opposed to simply greater-than, or less-than compare statements.
+
TBD
  
==Discussion ==
+
==Related [[Attacks]]==
  
Unchecked array indexing, depending on its instantiation, can be responsible for any number of related issues. Most prominent of these possible flaws is the buffer overflow condition. Due to this fact, consequences range from denial of service, and data corruption, to full blown arbitrary code execution
+
* [[Attack 1]]
 +
* [[Attack 2]]
  
The most common condition situation leading to unchecked array indexing is the use of loop index variables as buffer indexes. If the end condition for the loop is subject to a flaw, the index can grow or shrink unbounded, therefore causing a buffer overflow or underflow.  Another common situation leading to this condition is the use of a function's return value, or the resulting value of a calculation directly as an index in to a buffer.
 
  
==Examples ==
+
==Related [[Vulnerabilities]]==
  
Not available.
+
* [[Buffer Overflow]] (and related issues)
 +
* [[Buffer Underwrite]]
 +
* [[Signed-to-Unsigned Conversion Error]]
 +
* [[Write-What-Where]]
  
==Related problems ==
 
  
* [[Buffer Overflow]] (and related issues)
+
==Related [[Controls]]==
  
* [[Buffer Underwrite]]
+
* Requirements specification: The choice could be made to use a language that is not susceptible to these issues.
 +
* Implementation: Include sanity checks to ensure the validity of any values used as index variables. In loops, use greater-than-or-equal-to, or less-than-or-equal-to, as opposed to simply greater-than, or less-than compare statements.
  
* [[Signed-to-Unsigned Conversion Error]]
 
  
* [[Write-What-Where]]
 
  
==Categories ==
+
==Related [[Technical Impacts]]==
  
[[Category:Vulnerability]]
+
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
  
[[Category:Range and Type Errors]]
+
 
 +
==References==
 +
 
 +
TBD
 +
[[Category:FIXME|add links
 +
 
 +
In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>
 +
 
 +
Availability Vulnerability
 +
 
 +
Authorization Vulnerability
 +
 
 +
Authentication Vulnerability
 +
 
 +
Concurrency Vulnerability
 +
 
 +
Configuration Vulnerability
 +
 
 +
Cryptographic Vulnerability
 +
 
 +
Encoding Vulnerability
 +
 
 +
Error Handling Vulnerability
 +
 
 +
Input Validation Vulnerability
 +
 
 +
Logging and Auditing Vulnerability
 +
 
 +
Session Management Vulnerability]]
 +
 
 +
__NOTOC__
 +
 
 +
 
 +
[[Category:OWASP ASDR Project]]
 +
[[Category:Vulnerability]]
 +
[[Category:Range and Type Error Vulnerability]]
 +
[[Category:OWASP_CLASP_Project]]

Latest revision as of 07:50, 3 June 2009

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



Last revision (mm/dd/yy): 06/3/2009

Vulnerabilities Table of Contents

Description

Unchecked array indexing occurs when an unchecked value is used as an index into a buffer.

Consequences

  • Availability: Unchecked array indexing will very likely result in the corruption of relevant memory and perhaps instructions, leading to a crash, if the values are outside of the valid memory area
  • Integrity: If the memory corrupted is data, rather than instructions, the system will continue to function with improper values.
  • Access Control: If the memory corrupted memory can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow.

Exposure period

  • Requirements specification: The choice could be made to use a language that is not susceptible to these issues.
  • Implementation: Many logic errors can lead to this condition. It can be exacerbated by lack of or misuse of mitigating technologies.

Platform

  • Languages: C, C++, Assembly
  • Operating Platforms: All

Required resources

Any

Severity

Medium

Likelihood of exploit

Medium

Unchecked array indexing, depending on its instantiation, can be responsible for any number of related issues. Most prominent of these possible flaws is the buffer overflow condition. Due to this fact, consequences range from denial of service, and data corruption, to full blown arbitrary code execution

The most common condition situation leading to unchecked array indexing is the use of loop index variables as buffer indexes. If the end condition for the loop is subject to a flaw, the index can grow or shrink unbounded, therefore causing a buffer overflow or underflow. Another common situation leading to this condition is the use of a function's return value, or the resulting value of a calculation directly as an index in to a buffer.


Risk Factors

TBD

Examples

TBD

Related Attacks


Related Vulnerabilities


Related Controls

  • Requirements specification: The choice could be made to use a language that is not susceptible to these issues.
  • Implementation: Include sanity checks to ensure the validity of any values used as index variables. In loops, use greater-than-or-equal-to, or less-than-or-equal-to, as opposed to simply greater-than, or less-than compare statements.


Related Technical Impacts


References

TBD