From checkmk-werks-lvl1@lists.checkmk.com Wed May 29 14:46:28 2024
From: Checkmk werks level 1 <checkmk-werks-lvl1@lists.checkmk.com>
To: checkmk-werks-lvl1@lists.checkmk.com
Subject: [2.3.0] Checkmk Werk 15843 created: mk_oracle(ps1): Follow-up to
 privilege escalation fix
Date: Wed, 29 May 2024 14:46:27 +0000
Message-ID: <1716993987.321768.13084.nullmailer@localhost>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6118000506714439415=="

--===============6118000506714439415==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

[//]: # (werk v2)
# mk_oracle(ps1): Follow-up to privilege escalation fix

key        | value
---------- | ---
compatible | no
version    | 2.3.0b5
date       | 2024-04-05T11:02:27+00:00
level      | 2
class      | fix
component  | checks
edition    | cre

You might be affected by this Werk if you use <tt>mk_oracle</tt> on Windows.

Werk <a href=3D"https://checkmk.com/werk/16232">Werk #16232</a> introduced a =

regression, thereby disrupting Oracle monitoring on Windows.

This Werk addresses above mentioned issue that affects versions 2.1.0p41,=20
2.2.0p24, and 2.3.0b4.

Since this release, Oracle monitoring on Windows is fully supported under=20
condition you use an account without administrator rights or the certain=20
executable binaries, <tt>sqlplus.exe</tt>, <tt>tnsping.exe</tt> and, if=20
presented, <tt>crsctl.exe</tt> are write-protected, with the possible=20
exception being the Administrator.

If you are unable or prefer not to use an unprivileged account then you may=20
need to adjust permissions for above mentioned binaries: remove <tt>Write</tt=
>,=20
<tt>Full Control</tt> and <tt>Modify</tt> permissions for any non-Administrat=
or=20
user and group.

More information about can be found at <a href=3D"https://checkmk.atlassian.n=
et/wiki/x/AQA1B">here</a>.


--===============6118000506714439415==--