CWE-823 Use of Out-of-range Pointer Offset

The product performs pointer arithmetic on a valid pointer, but it uses an offset that can point outside of the intended range of valid memory locations for the resulting pointer.

The offset might be out-of-range if it comes from an untrusted source, is the result of an incorrect calculation, or occurs because of another error. If an attacker can control or influence the offset so that it points outside of the intended boundaries of the structure, then the attacker may be able to read or write to memory locations that are used elsewhere in the product. As a result, the attack might change the state of the product as accessed through program variables, cause a crash or instable behavior, and possibly lead to code execution.

• Confidentiality: Read Memory — If the untrusted pointer is used in a read operation, an attacker might be able to read sensitive portions of memory. • Availability: DoS: Crash, Exit, or Restart — If the untrusted pointer references a memory location that is not accessible to the program, or points to a location that is "malformed" or larger than expected by a read or write operation, the application may terminate unexpectedly. • Integrity, Confidentiality, Availability: Execute Unauthorized Code or Commands, Modify Memory — If the untrusted pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.) • Automated Dynamic Analysis: Use tools that are integrated during compilation to insert runtime error-checking mechanisms related to memory safety errors, such as AddressSanitizer (ASan) for C/C++ [REF-1518].

• CVE-2010-2160: Invalid offset in undocumented opcode leads to memory corruption. • CVE-2010-1281: Multimedia player uses untrusted value from a file when using file-pointer calculations. • CVE-2009-3129: Spreadsheet program processes a record with an invalid size field, which is later used as an offset. • CVE-2009-2694: Instant messaging library does not validate an offset value specified in a packet. • CVE-2009-2687: Language interpreter does not properly handle invalid offsets in JPEG image, leading to out-of-bounds memory access and crash. • CVE-2009-0690: negative offset value leads to out-of-bounds read • CVE-2008-4114: untrusted offset in kernel • CVE-2010-2873: "blind trust" of an offset value while writing heap memory allows corruption of function pointer,leading to code execution • CVE-2010-2866: negative value (signed) causes pointer miscalculation • CVE-2010-2872: signed values cause incorrect pointer calculation • CVE-2007-5657: values used as pointer offsets • CVE-2010-2867: a return value from a function is sign-extended if the value is signed, then used as an offset for pointer arithmetic • CVE-2009-1097: portions of a GIF image used as offsets, causing corruption of an object pointer. • CVE-2008-1807: invalid numeric field leads to a free of arbitrary memory locations, then code execution. • CVE-2007-2500: large number of elements leads to a free of an arbitrary address • CVE-2008-1686: array index issue (CWE-129) with negative offset, used to dereference a function pointer • CVE-2010-2878: "buffer seek" value - basically an offset?