Bug 33360

Summary:	ipmitool crashes on v2.0 protocol (lanplus option)
Product:	Mageia	Reporter:	Chris Denice <eatdirt>
Component:	RPM Packages	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	andrewsfarm, eatdirt, geiger.david68210, sysadmin-bugs
Version:	9	Keywords:	advisory, validated_update
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	MGA9-64-OK
Source RPM:	ipmitool-1.8.18-10.mga9.src.rpm	CVE:
Status comment:

Description Chris Denice 2024-07-03 15:17:13 CEST

Description of problem:

Trying to access the BMC of a remote server having a IMPI v2.0 management interface, let's call it  "pippo" machine:

ipmitool -I lanplus -H pippo -U admin

produces a segfault just after the (right) password is entered. This occurs only with the "lanplus" protocol, IPMI v1.5 with "lan" protocol works as expected. But the machine "pippo" I am interested in supports only IMPI v2.0, so it is basically unusable for it.

The segfault is within libcrypto (which is somehow expected as lanplus is encrypted)

ipmitool[175559]: segfault at 6c ip 00007f11b460289c sp 00007ffc8fa99780 error 6 in libcrypto.so.3[7f11b44ac000+2bb000] likely on CPU 1 (core 1, socket 0).


I have tested the latest version of ipmitool (which is in cauldron, versio 1.8.19) and it works fine with the exact same command. Maybe we just need to update it to that version on mga9, provided there is no side effect. I did not do it as the package as a maintainer.

Cheers,
Chris.

Comment 1 David GEIGER 2024-07-03 16:23:49 CEST

$ mgarepo maintdb get ipmitool
philippem

philippem is no more active for a while so you can work on this package without problem!

CC: (none) => geiger.david68210

Comment 2 Chris Denice 2024-07-03 16:35:06 CEST

Ok, I'll do that!

Comment 3 Lewis Smith 2024-07-03 20:46:32 CEST

Thank you Chris both for the report, and the offer to sort the issue (which does not occur with Cauldron) for Mageia 9.
Hence assigning this to you.

Assignee: bugsquad => eatdirt

Comment 4 Chris Denice 2024-07-03 23:22:26 CEST

ipmitool version 1.8.19 landing in core/updates_testing

The testing might be a bit problematic as you need a machine with special hardware, having a BMC. If you don't know what I am talking about, here it is: https://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface

Basic Test:
-----
Assuming your computer has a motherboard with BMC, various modules should be automagically loaded by the kernel (ipmi_devintf...). Then as root, after installing ipmitool-1.8.19, run, on that machine, in a terminal:

ipmitool shell

You're entering a shell, if it is not crashing, we're good.
-----

Debug Test:
-----
To reproduce the bug, you need a BMC with a management network interface, assumed to be upo, configured and running on say 192.168.1.128. From *another machine*, on which you have installed ipmitool-1.8.19, you connect to its BMC with the IPMI v2.0 protocol (called lanplus) as:

ipmitool -I lanplus -H 192.168.1.128 -U thenameoftheadmin

A prompt asks you for a password (assumed to be configured), entering the correct password with 1.8.19 works, entering the correct password with 1.8.18 segfaults.

I have done that on x86_64 with hardware HP ProLiant DL360p Gen8.



Suggested advisory:
========================

Updated ipmitool to version 1.8.19 to fix a segfault while accessing a remote BMC using the lanplus protocol (IPMI v2.0).

========================

Updated packages in core/updates_testing:
========================
ipmitool-1.8.19-1.mga9


Source RPMs: 
ipmitool-1.8.19-1.mga9.src.rpm

CC: (none) => eatdirt
Assignee: eatdirt => qa-bugs

katnatek 2024-07-04 00:27:35 CEST

Keywords: (none) => advisory

Comment 5 katnatek 2024-07-04 03:16:58 CEST

LC_ALL=C urpmi ipmitool

    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/ipmitool-1.8.18-10.mga9.x86_64.rpm
installing ipmitool-1.8.18-10.mga9.x86_64.rpm from /var/cache/urpmi/rpms                                                            
Preparing...                     ##################################################################################################
      1/1: ipmitool              ##################################################################################################

LC_ALL=C urpmi --auto --auto-update
medium "QA Testing (32-bit)" is up-to-date
medium "QA Testing (64-bit)" is up-to-date
medium "Core Release (distrib1)" is up-to-date
medium "Core Updates (distrib3)" is up-to-date
medium "Nonfree Release (distrib11)" is up-to-date
medium "Nonfree Updates (distrib13)" is up-to-date
medium "Tainted Release (distrib21)" is up-to-date
medium "Tainted Updates (distrib23)" is up-to-date
medium "Core 32bit Release (distrib31)" is up-to-date
medium "Core 32bit Updates (distrib32)" is up-to-date
medium "Nonfree 32bit Release (distrib36)" is up-to-date
medium "Tainted 32bit Release (distrib41)" is up-to-date
medium "Tainted 32bit Updates (distrib42)" is up-to-date

installing ipmitool-1.8.19-1.mga9.x86_64.rpm from //home/katnatek/qa-testing/x86_64
Preparing...                     ##################################################################################################
      1/1: ipmitool              ##################################################################################################
      1/1: removing ipmitool-1.8.18-10.mga9.x86_64
                                 ##################################################################################################

As reporter is the packager and say it works and the package clean install I give OK

Whiteboard: (none) => MGA9-64-OK
CC: (none) => andrewsfarm

Comment 6 Thomas Andrews 2024-07-04 14:21:47 CEST

I looked into trying the basic test, but since the modules listed in comment 4 aren't installed, my hardware must not be up to the job. 

Validating on the clean install.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 7 Mageia Robot 2024-07-04 18:48:50 CEST

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0156.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED