Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15938 discussions

[2.2.0] Checkmk Werk 16037 created: folder_config/host_config: No longer accept non-existent site

by Checkmk werks level 1

Title: folder_config/host_config: No longer accept non-existent site Class: fix Compatible: compat Component: rest-api Date: 1703232688 Edition: cre Level: 1 Version: 2.2.0p19 You can no longer set a non-existent site on folders and hosts. When called with a non-existent site as an attribute the endpoints now return the status code 400.

8 months, 2 weeks

[2.2.0] Checkmk Werk 16273 created: Local privilege escalation in agent plugin 'mk_tsm'

by Checkmk werks level 1

Title: Local privilege escalation in agent plugin 'mk_tsm' Class: security Compatible: incomp Component: checks Date: 1702411459 Edition: cre Level: 1 Version: 2.2.0p18 By crafting a malicious command that then shows up in the output of <code>ps</code> users of monitored hosts could gain root privileges. This was achieved by exploiting the insufficient quoting when using ksh's <code>eval</code> to create the required environment. This issue was found during internal review. <h3>Affected Versions</h3> LI: 2.2.0 LI: 2.1.0 LI: 2.0.0 (EOL) and older <h3>Mitigations</h3> If updating is not possible, disable the Tivoli Storage Manager plugin. <h3>Vulnerability Management</h3> We have rated the issue with a CVSS score of 8.8 (High) with the following CVSS vector: <code>CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H</code> We have assigned <code>CVE-2023-6735</code>. <h3>Changes</h3> With this change we no longer use <code>eval</code> and fixe the quoting. This prevents variable exports being missinterpreted as commands to execute.

8 months, 2 weeks

[2.2.0] Checkmk Werk 16227 created: Disabled automation users could still authenticate

by Checkmk werks level 1

Title: Disabled automation users could still authenticate Class: security Compatible: incomp Component: wato Date: 1702309789 Edition: cre Level: 1 Version: 2.2.0p18 Prior to this Werk an automation user whose password was disabled also described as "disable the login to this account" was still able to authenticate. The information that a user was disabled was not checked for automation users. We found this vulnerability internally. <b>Affected Versions</b>: * 2.2.0 * 2.1.0 * 2.0.0 * 1.6.0 * 1.5.0 (probably older versions as well) <b>Mitigations</b>: If the need arises to block an automation user one can change the password or remove that user from the system. <b>Vulnerability Management</b>: We have rated the issue with a CVSS Score of 8.8 (High) with the following CVSS vector: <tt>CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H</tt>. We assigned CVE-2023-31211 to this vulnerability. <b>Changes</b>: This Werk adds a check for the disabled information. During update you will be warned if a automation user is currently disabled.

8 months, 2 weeks

[2.2.0] Checkmk Werk 16163 created: jar_signature: Prevent privilege escalation to root

by Checkmk werks level 1

Title: jar_signature: Prevent privilege escalation to root Class: security Compatible: incomp Component: checks Date: 1702395666 Edition: cre Level: 3 Version: 2.2.0p18 jar_signature agent plugin (configured by the 'Signatures of certificates in JAR files' bakery rule) was vulnerable to privilege escalation to root by the oracle user. A malicious oracle user could replace the jarsigner binary with another script and put it in the JAVA_HOME directory. The script would be executed by the root user. The jarsigner is now executed by the oracle user, preventing the privilege escalation. This werk is incompatible for users that use the jar_signature plugin. Too avoid risk, users should deploy the new version of the plugin or disable it. This issue was found during internal review. <h3>Affected Versions</h3> LI: 2.2.0 LI: 2.1.0 LI: 2.0.0 (EOL) and older <h3>Mitigations</h3> If updating is not possible, disable the jar_signature plugin. <h3>Vulnerability Management</h3> We have rated the issue with a CVSS score of 8.8 (High) with the following CVSS vector: <code>CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H</code> We have assigned <code>CVE-2023-6740</code>. <h3>Changes</h3> The jarsigner binary is now executed by the oracle user.

8 months, 2 weeks

[2.2.0] Checkmk Werk 16165 created: check_mk_agent: Set LC_ALL before running the agent

by Checkmk werks level 1

Title: check_mk_agent: Set LC_ALL before running the agent Class: fix Compatible: compat Component: checks Date: 1704190188 Edition: cre Level: 1 Version: 2.2.0p18 Previously, Checkmk agents would be run with a preset LC_ALL environment variable if neither C.UTF-8 or C.utf-8 locales were installed. That led to invalid agent output and crashes in section parsing in multiple checks for some of the locales. Linux, AIX, Solaris, FreeBSD and OpenWrt agents were affected. Now, LC_ALL variable is set to C for the described case.

8 months, 2 weeks

[2.2.0] Checkmk Werk 16038 created: SLA tooltip missing UNKN state

by Checkmk werks level 1

Title: SLA tooltip missing UNKN state Class: fix Compatible: compat Component: multisite Date: 1704356932 Edition: cee Level: 1 Version: 2.2.0p18 The SLA tooltip would always show UNKN (0%) even if the state was UNKN. The corresponding value was aggregated as a PEND state. Now the UNKN state is displayed correctly.

8 months, 2 weeks

[2.2.0] Checkmk Werk 15717 created: NagVis: Updated to 1.9.40

by Checkmk werks level 1

Title: NagVis: Updated to 1.9.40 Class: fix Compatible: compat Component: packages Date: 1704797005 Edition: cre Level: 1 Version: 2.2.0p18

8 months, 2 weeks

[2.2.0] Checkmk Werk 16147 created: Abort CMC on irrecoverable filesystem errors

by Checkmk werks level 1

Title: Abort CMC on irrecoverable filesystem errors Class: fix Compatible: compat Component: cmc Date: 1704295653 Edition: cee Level: 1 Version: 2.2.0p18 The errors LI: too many files open (EMFILE) LI: too many files open in system (ENFILE) LI: no buffer space (ENOBUFS) LI: not enough memory (ENOMEM) now exit the core. Correct monitoring cannot be guaranteed when the server is in this state.

8 months, 2 weeks

[2.2.0] Checkmk Werk 16194 created: Licensing: Allow UI to be used in trial and free state when CMC is not running

by Checkmk werks level 1

Title: Licensing: Allow UI to be used in trial and free state when CMC is not running Class: fix Compatible: compat Component: wato Date: 1704716713 Edition: cce Level: 1 Version: 2.2.0p18 When using a CCE in the trial phase or in the free license state, the UI was mostly unusable when the CMC was not running (with the pages showing the error "Cannot connect to 'unix:/omd/sites/monitoring_eval/tmp/run/live'....") Since the CMC is prohibited from starting if too many services are being monitored in the free license state, this meant that in order to get out of the free state, the license could only be applied via REST-API. This has now been fixed.

8 months, 2 weeks

[2.2.0] Checkmk Werk 16164 adapted: veeam_cdp_jobs: Handle last sync time from the future

by Checkmk werks level 1

Werk 16164 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: veeam_cdp_jobs: Handle last sync time from the future Class: fix Compatible: compat Component: checks Date: 1703838299 Edition: cre Level: 1 Version: 2.2.0p18 Previously, the veeam_cdp_jobs would crash when receiving last sync time from the future with a message: C+: raise ValueError("Cannot render negative timespan") C-: Now, the affected service will be in state WARN and report the following message: C+: "The timestamp of the file is in the future. Please investigate your host times" C-: ------------------------------------<diff>------------------------------------------- Title: veeam_cdp_jobs: Handle last sync time from the future Class: fix Compatible: compat Component: checks Date: 1703838299 Edition: cre Level: 1 Version: 2.2.0p18 Previously, the veeam_cdp_jobs would crash when receiving last sync time from the future with a message: C+: raise ValueError("Cannot render negative timespan") C-: - Now, the time since the last job run will be 0 for such cases. + Now, the affected service will be in state WARN and report the following message: + C+: + "The timestamp of the file is in the future. Please investigate your host times" + C-:

8 months, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1