From checkmk-werks-lvl1@lists.checkmk.com Thu Apr 18 12:53:39 2024 From: Checkmk werks level 1 To: checkmk-werks-lvl1@lists.checkmk.com Subject: [2.2.0] Checkmk Werk 15327 created: mk_oracle: Follow-up to privilege escalation fix Date: Thu, 18 Apr 2024 12:53:37 +0000 Message-ID: <1713444817.650590.725.nullmailer@localhost> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7188792124590693315==" --===============7188792124590693315== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Title: mk_oracle: Follow-up to privilege escalation fix Class: fix Compatible: incomp Component: checks Date: 1712217578 Edition: cre Level: 2 Version: 2.2.0p25 You might be affected by this Werk if you use mk_oracle on a unix system. You might be affected by this Werk if you use oracle wallet to connect to your database. You are definitively affected by this Werk if you use oracle wallet to connec= t to your database and used the instructions of our official documentation to setup your configuration. This Werk fixes connection problems introduced with 2.1.0p41, 2.2.0p24 and 2.= 3.0b4. Since Werk #16232 we switch to= a unprivileged user when executing oracle binaries. This causes problems when using an oracle wallet as the unprivileged user might not be able to access files defining the connection details and credentials. We introduced an additional permission check to the -t "Just che= ck the connection" option of mk_oracle. It should help you modifying the permissions to continue using mk_oracle with oracle wallet. You can execute it with the following command:
MK_CONFDIR=3D/etc/check_mk/ MK_VARDIR=3D/var/lib/check_mk_agent /usr/lib/chec=
k_mk_agent/plugins/mk_oracle --no-spool -t
The path to mk_oracle might be different if you execute it asynchronously. Fo= r a 60 second interval the path would be /usr/lib/check_mk_agent/plugins/60= /mk_oracle The script will test permissions of the files needed to connect to the databa= se. It boils down to the following: mk_oracle will switch to the owner of $ORACLE_HOME/bin/sqlplus before executing sqlplus. = So this user has to have the following permissions: Beside that we also fixed some bash syntax errors we introduced with Werk #16232. See Troubleshooting mk_oracle for = Windows and Linux for more information about troubleshooting this problem. --===============7188792124590693315==--