ipmi-oem in FreeIPMI before 1.6.18 has exploitable buffer overflows on response messages. The Intelligent Platform Management Interface (IPMI) specification defines a set of interfaces for platform management. It is implemented by a large number of hardware manufacturers to support system management. It is most commonly used for sensor reading (e.g., CPU temperatures through the ipmi-sensors command within FreeIPMI) and remote power control (the ipmipower command). The ipmi-oem client command implements a set of a IPMI OEM commands for specific hardware vendors. If a user has supported hardware, they may wish to use the ipmi-oem command to send a request to a server to retrieve specific information. Two subcommands ipmi-oem dell get-active-directory-config and ipmi-oem fujitsu get-sel-entry-long-text were found to have exploitable buffer overflows on response messages.
Weakness
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | RedHat | freeipmi-0:1.6.18-1.el10_2 | * |
| Red Hat Enterprise Linux 8 | RedHat | freeipmi-0:1.6.18-1.el8_10 | * |
| Red Hat Enterprise Linux 9 | RedHat | freeipmi-0:1.6.18-1.el9_8 | * |
| Freeipmi | Ubuntu | esm-infra-legacy/trusty | * |
| Freeipmi | Ubuntu | esm-infra-legacy/xenial | * |
| Freeipmi | Ubuntu | esm-infra/bionic | * |
| Freeipmi | Ubuntu | esm-infra/focal | * |
| Freeipmi | Ubuntu | jammy | * |
| Freeipmi | Ubuntu | noble | * |
| Freeipmi | Ubuntu | questing | * |
| Freeipmi | Ubuntu | resolute | * |
| Freeipmi | Ubuntu | upstream | * |
Potential Mitigations
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
- D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
- Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
- For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].