CWE-129Improper Validation of Array Index

Description

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

Common consequences

• Integrity,Availability→DoS: Crash, Exit, or Restart
  Use of an index that is outside the bounds of an array 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→Modify Memory
  If the memory corrupted is data, rather than instructions, the system will continue to function with improper values.
• Confidentiality,Integrity→Modify Memory,Read Memory
  Use of an index that is outside the bounds of an array can also trigger out-of-bounds read or write operations, or operations on the wrong objects; i.e., "buffer overflows" are not always the result. This may result in the exposure or modif
• Integrity,Confidentiality,Availability→Execute Unauthorized Code or Commands
  If the memory accessible by the attacker can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow and possibly without the use of large inputs if a precise index can be controlled.
• Integrity,Availability,Confidentiality→DoS: Crash, Exit, or Restart,Execute Unauthorized Code or Commands,Read Memory,Modify Memory
  A single fault could allow either an overflow (CWE-788) or underflow (CWE-786) of the array index. What happens next will depend on the type of operation being performed out of bounds, but can expose sensitive information, cause a system cr

Potential mitigations

• Architecture and Design
  Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
• Architecture and Design
  [object Object]
• Requirements
  [object Object]
• Operation,Build and Compilation
  [object Object]
• Operation
  [object Object]
• Implementation
  [object Object]
• Implementation
  Be especially careful to validate all input when invoking code that crosses language boundaries, such as from an interpreted language to native code. This could create an unexpected interaction between the language boundaries. Ensure that you are not violating any of the expectations of the language with which you are interfacing. For example, even though Java may not be susceptible to buffer over
• Architecture and Design,Operation
  Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database ad
• Architecture and Design,Operation
  [object Object]

Related CWEs

Recent CVEs classified under this CWE