CVE-2013-3607 - Improper Restriction of Operations within the Bounds of a Memory Buffer

Severity

99%

Complexity

99%

Confidentiality

165%

Multiple stack-based buffer overflows in the web interface in the Intelligent Platform Management Interface (IPMI) implementation on Supermicro H8DC*, H8DG*, H8SCM-F, H8SGL-F, H8SM*, X7SP*, X8DT*, X8SI*, X9DAX-*, X9DB*, X9DR*, X9QR*, X9SBAA-F, X9SC*, X9SPU-F, and X9SR* devices allow remote attackers to execute arbitrary code on the Baseboard Management Controller (BMC), as demonstrated by the (1) username or (2) password field in login.cgi.

Multiple stack-based buffer overflows in the web interface in the Intelligent Platform Management Interface (IPMI) implementation on Supermicro H8DC*, H8DG*, H8SCM-F, H8SGL-F, H8SM*, X7SP*, X8DT*, X8SI*, X9DAX-*, X9DB*, X9DR*, X9QR*, X9SBAA-F, X9SC*, X9SPU-F, and X9SR* devices allow remote attackers to execute arbitrary code on the Baseboard Management Controller (BMC), as demonstrated by the (1) username or (2) password field in login.cgi.

CVSS 2.0 Base Score 9.9. CVSS Attack Vector: network. CVSS Attack Complexity: low. CVSS Vector: (AV:N/AC:L/Au:N/C:C/I:C/A:C).

Demo Examples

Improper Restriction of Operations within the Bounds of a Memory Buffer

CWE-119

This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.


               
}
strcpy(hostname, hp->h_name);/*routine that ensures user_supplied_addr is in the right format for conversion */

This function allocates a buffer of 64 bytes to store the hostname, however there is no guarantee that the hostname will not be larger than 64 bytes. If an attacker specifies an address which resolves to a very large hostname, then we may overwrite sensitive data or even relinquish control flow to the attacker.

Note that this example also contains an unchecked return value (CWE-252) that can lead to a NULL pointer dereference (CWE-476).

Improper Restriction of Operations within the Bounds of a Memory Buffer

CWE-119

This example applies an encoding procedure to an input string and stores it into a buffer.


               
}
return dst_buf;
die("user string too long, die evil hacker!");
else dst_buf[dst_index++] = user_supplied_string[i];
dst_buf[dst_index++] = ';';
/* encode to < */

The programmer attempts to encode the ampersand character in the user-controlled string, however the length of the string is validated before the encoding procedure is applied. Furthermore, the programmer assumes encoding expansion will only expand a given character by a factor of 4, while the encoding of the ampersand expands by 5. As a result, when the encoding procedure expands the string it is possible to overflow the destination buffer if the attacker provides a string of many ampersands.

Improper Restriction of Operations within the Bounds of a Memory Buffer

CWE-119

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


               
}
printf("You 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).

Improper Restriction of Operations within the Bounds of a Memory Buffer

CWE-119

In the following code, the method retrieves a value from an array at a specific array index location that is given as an input parameter to the method


               
}
return value;// check that the array index is less than the maximum// length of the array
value = array[index];// get the value at the specified index of the array
// if array index is invalid then output error message// and return value indicating error
value = -1;

However, this method only verifies that the given array index is less than the maximum length of the array but does not check for the minimum value (CWE-839). This will allow a negative value to be accepted as the input array index, which will result in a out of bounds read (CWE-125) and may allow access to sensitive memory. The input array index should be checked to verify that is within the maximum and minimum range required for the array (CWE-129). In this example the if statement should be modified to include a minimum range check, as shown below.


               
...// check that the array index is within the correct// range of values for the array

Improper Restriction of Operations within the Bounds of a Memory Buffer

CWE-119

Windows provides the _mbs family of functions to perform various operations on multibyte strings. When these functions are passed a malformed multibyte string, such as a string containing a valid leading byte followed by a single null byte, they can read or write past the end of the string buffer causing a buffer overflow. The following functions all pose a risk of buffer overflow: _mbsinc _mbsdec _mbsncat _mbsncpy _mbsnextc _mbsnset _mbsrev _mbsset _mbsstr _mbstok _mbccpy _mbslen

Overview

Type

SuperMicro

First reported 11 years ago

2013-09-08 03:17:00

Last updated 7 years ago

2017-11-15 02:29:00

Affected Software

SuperMicro H8DCL-6F

SuperMicro H8DCL-IF

SuperMicro H8DCT-HIBQF

SuperMicro H8DCT-HLN4F

SuperMicro H8DCT-IBQF

SuperMicro H8DG6-F

SuperMicro H8DGG-QF

SuperMicro H8DGI-F

SuperMicro H8DGT-HF

SuperMicro H8DGT-HIBQF

SuperMicro H8DGT-HLF

SuperMicro H8DGT-HLIBQF

SuperMicro H8DGU-F

SuperMicro H8DGU-LN4F+

SuperMicro H8SCM-F

SuperMicro H8SQL-F

SuperMicro H8SME-F

SuperMicro H8SML-7

SuperMicro H8SML-7F

SuperMicro H8SML-I

SuperMicro H8SML-IF

SuperMicro X7SPA-HF

SuperMicro X7SPA-HF-525

SuperMicro X7SPE-H-D525

SuperMicro X7SPE-HF

SuperMicro X7SPE-HF-D525

SuperMicro X7SPT-DF-D525

SuperMicro X7SPT-DF-D525+

SuperMicro X8DTL-3F

SuperMicro X8DTL-6F

SuperMicro X8DTL-IF

SuperMicro X8DTN+-F

SuperMicro X8DTN+-F-LR

SuperMicro X8DTU-6+

SuperMicro X8DTU-6+-LR

SuperMicro X8DTU-6TF+

SuperMicro X8DTU-6TF+-LR

SuperMicro X8DTU-LNF+

SuperMicro X8DTU-LN4F+-LR

SuperMicro X8SI6-F

SuperMicro X8SIA-F

SuperMicro X8SIE-F

SuperMicro X8SIE-LN4F

SuperMicro X8SIL-T

SuperMicro X8SIT-F

SuperMicro X8SIT-HF

SuperMicro X8SIU-F

SuperMicro X9DAX-7F

SuperMicro X9DAX-7F-HFT

SuperMicro X9DAX-7TF

SuperMicro X9DAX-IF

SuperMicro X9DAX-IF-HFT

SuperMicro X9DAX-ITF

SuperMicro X9DB3-F

SuperMicro X9DB3-TPF

SuperMicro X9DBI-F

SuperMicro X9DBI-TPF

SuperMicro X9DBL-3F

SuperMicro X9DBL-IF

SuperMicro X9DBU-3F

SuperMicro X9DBU-IF

SuperMicro X9DR3-F

SuperMicro X9DR3-LN4F+

SuperMicro X9DR7-LN4F

SuperMicro X9DR7-LN4F-JBOD

SuperMicro X9DR7-TF+

SuperMicro X9DRD-7JLN4F

SuperMicro X9DRD-7LN4F

SuperMicro X9DRD-7LN4F-JBOD

SuperMicro X9DRD-EF

SuperMicro X9DRD-IF

SuperMicro X9DRE-LN4F

SuperMicro X9DRE-TF+

SuperMicro X9DRFF

SuperMicro X9DRFF-7

SuperMicro X9DRFF-7+

SuperMicro X9DRFF-7G+

SuperMicro X9DRFF-7T+

SuperMicro X9DRFF-7TG+

SuperMicro X9DRFF-I+

SuperMicro X9DRFF-IG+

SuperMicro X9DRFF-IT+

SuperMicro X9DRFF-ITG+

SuperMicro X9DRFR

SuperMicro X9DRG-HF

SuperMicro X9DRG-HF+

SuperMicro X9DRG-HTF

SuperMicro X9DRG-HTF+

SuperMicro X9DRH-7F

SuperMicro X9DRH-7TF

SuperMicro X9DRH-IF

SuperMicro X9DRH-ITF

SuperMicro X9DRI-F

SuperMicro X9DRI-LN4F+

SuperMicro X9DRL-3F

SuperMicro X9DRL-EF

SuperMicro X9DRL-IF

SuperMicro X9DRT-F

SuperMicro X9DRT-H6F

SuperMicro X9DRT-H6IBFF

SuperMicro X9DRT-H6IBQF

SuperMicro X9DRT-HF+

SuperMicro X9DRT-IBFF

SuperMicro X9DRT-IBQF

SuperMicro X9DRW-3LN4+

SuperMicro X9DRW-3TF+

SuperMicro X9DRW-7TPF+

SuperMicro X9DRW-ITPF+

SuperMicro X9DRX+-F

SuperMicro X9QR7-TF

SuperMicro X9QR7-TF+

SuperMicro X9QR7-TF-JBOD

SuperMicro X9QRI-F

SuperMicro X9QRI-F+

SuperMicro X9SBAA-F

SuperMicro X9SCA-F

SuperMicro X9SCD-F

SuperMicro X9SCE-F

SuperMicro X9SCFF-F

SuperMicro X9SCI-LN4F

SuperMicro X9SCL+-F

SuperMicro X9SCL-F

SuperMicro X9SCM-F

SuperMicro X9SCM-IIF

SuperMicro X9SPU-F

SuperMicro X9SRD-F

SuperMicro X9SRE-3F

SuperMicro X9SRE-F

SuperMicro X9SRG-F

SuperMicro X9SRI-3F

SuperMicro X9SRI-F

SuperMicro X9SRL-F

SuperMicro X9SRW-F

Stay updated

ExploitPedia is constantly evolving. Sign up to receive a notification when we release additional functionality.

Get in touch

If you'd like to report a bug or have any suggestions for improvements then please do get in touch with us using this form. We will get back to you as soon as we can.