Improper Validation of Specified Index, Position, or Offset in Input

The product receives input that is expected to specify an index, position, or offset into an indexable resource such as a buffer or file, but it does not validate or incorrectly validates that the specified index/position/offset has the required properties.


Description

Often, indexable resources such as memory buffers or files can be accessed using a specific position, index, or offset, such as an index for an array or a position for a file. When untrusted input is not properly validated before it is used as an index, attackers could access (or attempt to access) unauthorized portions of these resources. This could be used to cause buffer overflows, excessive resource allocation, or trigger unexpected failures.

Demonstrations

The following examples help to illustrate the nature of this weakness and describe methods or techniques which can be used to mitigate the risk.

Note that the examples here are by no means exhaustive and any given weakness may have many subtle varieties, each of which may require different detection methods or runtime controls.

Example One

The following example retrieves the sizes of messages for a pop3 mail server. The message sizes are retrieved from a socket that returns in a buffer the message number and the message size, the message number (num) and size (size) are extracted from the buffer and the message size is placed into an array using the message number for the array index.

/* capture the sizes of all messages */
int getsizes(int sock, int count, int *sizes) {

  ...
  char buf[BUFFER_SIZE];
  int ok;
  int num, size;

  // read values from socket and added to sizes array
  while ((ok = gen_recv(sock, buf, sizeof(buf))) == 0)
  {


    // continue read from socket until buf only contains '.'
    if (DOTLINE(buf))
      break;

    else if (sscanf(buf, "%d %d", &num, &size) == 2)
      sizes[num - 1] = size;


  }
    ...


}

In this example the message number retrieved from the buffer could be a value that is outside the allowable range of indices for the array and could possibly be a negative number. Without proper validation of the value to be used for the array index an array overflow could occur and could potentially lead to unauthorized access to memory addresses and system crashes. The value of the array index should be validated to ensure that it is within the allowable range of indices for the array as in the following code.

/* capture the sizes of all messages */
int getsizes(int sock, int count, int *sizes) {

  ...
  char buf[BUFFER_SIZE];
  int ok;
  int num, size;

  // read values from socket and added to sizes array
  while ((ok = gen_recv(sock, buf, sizeof(buf))) == 0)
  {


    // continue read from socket until buf only contains '.'
    if (DOTLINE(buf))
      break;

    else if (sscanf(buf, "%d %d", &num, &size) == 2) {

      if (num > 0 && num <= (unsigned)count)
        sizes[num - 1] = size;

      else


        /* warn about possible attempt to induce buffer overflow */
        report(stderr, "Warning: ignoring bogus data for message sizes returned by server.\n");



    }

  }
    ...


}

Example Two

In the following example the method displayProductSummary is called from a Web service servlet to retrieve product summary information for display to the user. The servlet obtains the integer value of the product number from the user and passes it to the displayProductSummary method. The displayProductSummary method passes the integer value of the product number to the getProductSummary method which obtains the product summary from the array object containing the project summaries using the integer value of the product number as the array index.

// Method called from servlet to obtain product information
public String displayProductSummary(int index) {


  String productSummary = new String("");

  try {
    String productSummary = getProductSummary(index);


  } catch (Exception ex) {...}

  return productSummary;

}

public String getProductSummary(int index) {
  return products[index];
}

In this example the integer value used as the array index that is provided by the user may be outside the allowable range of indices for the array which may provide unexpected results or cause the application to fail. The integer value used for the array index should be validated to ensure that it is within the allowable range of indices for the array as in the following code.

// Method called from servlet to obtain product information
public String displayProductSummary(int index) {


  String productSummary = new String("");

  try {
    String productSummary = getProductSummary(index);


  } catch (Exception ex) {...}

  return productSummary;

}

public String getProductSummary(int index) {

  String productSummary = "";

  if ((index >= 0) && (index < MAX_PRODUCTS)) {
    productSummary = products[index];
  }
  else {
    System.err.println("index is out of bounds");
    throw new IndexOutOfBoundsException();
  }

  return productSummary;

}

An alternative in Java would be to use one of the collection objects such as ArrayList that will automatically generate an exception if an attempt is made to access an array index that is out of bounds.

ArrayList productArray = new ArrayList(MAX_PRODUCTS);
...
try {
  productSummary = (String) productArray.get(index);
} catch (IndexOutOfBoundsException ex) {...}

Example Three

The following example asks a user for an offset into an array to select an item.

int main (int argc, char **argv) {
  char *items[] = {"boat", "car", "truck", "train"};
  int index = GetUntrustedOffset();
  printf("User selected %s\n", items[index-1]);
}

The programmer allows the user to specify which element in the list to select, however an attacker can provide an out-of-bounds offset, resulting in a buffer over-read (CWE-126).

See Also

Comprehensive Categorization: Improper Input Validation

Weaknesses in this category are related to improper input validation.

Data Validation Issues

Weaknesses in this category are related to a software system's components for input validation, output validation, or other kinds of validation. Validation is a freque...

Comprehensive CWE Dictionary

This view (slice) covers all the elements in CWE.

Entries with Maintenance Notes

CWE entries in this view have maintenance notes. Maintenance notes are an indicator that an entry might change significantly in future versions. This view was created...

Weaknesses Introduced During Implementation

This view (slice) lists weaknesses that can be introduced during implementation.


Common Weakness Enumeration content on this website is copyright of The MITRE Corporation unless otherwise specified. Use of the Common Weakness Enumeration and the associated references on this website are subject to the Terms of Use as specified by The MITRE Corporation.