Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15984 discussions

Check_MK Werk 6842: Fixed dashlet top offset in classic theme

by Lars Michelsen

ID: 6842 Title: Fixed dashlet top offset in classic theme Component: Multisite Level: 1 Class: Bug fix Version: 1.6.0i1 CMK-1147

5 years, 11 months

Check_MK Werk 6841: Fixed missing hostname in graph collection graph titles

by Lars Michelsen

ID: 6841 Title: Fixed missing hostname in graph collection graph titles Component: metrics Level: 1 Class: Bug fix Version: 1.6.0i1

5 years, 11 months

Check_MK Werk 6505: Avoid CMC crash during event helper restarts.

by Sven Panne

ID: 6505 Title: Avoid CMC crash during event helper restarts. Component: Core & setup Level: 1 Class: Bug fix Version: 1.6.0i1 When an event helper (for notifications/alerts) should be restarted, the Check_MK Micro Core could go into an infinite recursion, ultimately leading to a crash of the CMC itself. This has been fixed. CMK-1117

5 years, 11 months

Check_MK Werk 6787: Notification spooler: Fixed file path traversal vulnerability

by Lars Michelsen

ID: 6787 Title: Notification spooler: Fixed file path traversal vulnerability Component: Notifications Level: 2 Class: Security fix Version: 1.6.0i1 The notification daemon of one site connects to the notification daemon of another site to exchange notifications between both sites. The notification daemon was not validating the incoming data correctly which made it possible for an attacker that has access to the notification sending site to compromise the receiving site. Using this vulnerability it was possible to write write files in directories that are writable by the receiving site user. This could be used to gain access to the site.

5 years, 11 months

Check_MK Werk 6786: Livestatus proxy: Fixed file path traversal vulnerability

by Lars Michelsen

ID: 6786 Title: Livestatus proxy: Fixed file path traversal vulnerability Component: Livestatus Proxy Level: 2 Class: Security fix Version: 1.6.0i1 The livestatus proxy connects to the livestatus server of remote sites. One task is to fetch the inventory data of the remote site and replicate it to the master site to make client accesses faster. The livestatus proxy was not validating the incoming data correctly which made it possible for an attacker that has access to the remote sites to compromise the site the livestatus proxy daemon is running in. Using this vulnerability it was possible to write write files in directories that are writable by the liveproxy site user. This could be used to gain access to the liveproxy site.

5 years, 11 months

Check_MK Werk 6788: Notification spooler: Fixed deserialization of arbitrary input

by Lars Michelsen

ID: 6788 Title: Notification spooler: Fixed deserialization of arbitrary input Component: Notifications Level: 2 Class: Security fix Version: 1.6.0i1 The notification daemon of one site connects to the notification daemon of another site to exchange notifications between both sites. The messages that are sent between the notification daemons were encoded in an insecure format which allowed code injections between the communication partners. This means it was possible to inject code from one notification spooler to another. We have now changed the message format to a secure alternative which prevents code injections. To be able to perform this transition without loosing notifications and preventing subtile incompatibilities we decided to keep the new format disabled by default for all sites created with Check_MK 1.4 and 1.5. This means your installation will still be affected by this issue by default after updating. However, once you have updated all your sites to at least 1.4.0p37 in case of the 1.4.0 branch or or at least 1.5.0p7 in case of the 1.5.0 branch you can change the main configuration option "Notification Spooler insecure messages" to "off" and activate the new configuration. Once you have done this all notification spoolers will use the new secure message format. Please note that the 1.6 notification spoolers will always use the new message format and not be compatible to the old message format of the 1.5 notification spoolers anymore. If you plan to use 1.5 and 1.6 together during migration you will have to ensure that you use the new message format in your 1.5 sites.

5 years, 11 months

Check_MK Werk 5847: lnx_thermal: Fixed to only gather values of temp & type

by Óscar Nájera

ID: 5847 Title: lnx_thermal: Fixed to only gather values of temp & type Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0p6 The Linux agent collected too many values when hysteresis data was available and the check crashed. This has been fixed now by fixing the required values.

5 years, 11 months

Check_MK Werk 6807: veeam_tapejobs: Check returns 'Item not found' if no jobs are sent by the agent

by Simon Betz

ID: 6807 Title: veeam_tapejobs: Check returns 'Item not found' if no jobs are sent by the agent Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1

5 years, 11 months

Check_MK Werk 6751: SLES15: Fixed dependencies of gd

by Marcel Arentz

ID: 6751 Title: SLES15: Fixed dependencies of gd Component: Site Management Level: 1 Class: Bug fix Version: 1.6.0i1 In newer versions of SLES gd is only available if the module Desktop-Applications is activated. For Check_MK the package libgd3 is fully sufficient and available in all installations, so the depedencies changed from gd to libgd3.

5 years, 11 months

Check_MK Werk 5957: LDAP: Locking of users using "Authentication Expiration" plugin was not unlocking users

by Lars Michelsen

ID: 5957 Title: LDAP: Locking of users using "Authentication Expiration" plugin was not unlocking users Component: Multisite Level: 1 Class: Bug fix Version: 1.6.0i1 The LDAP sync can lock users in Check_MK based on their locking property in the Active Directory. When a user was locked in AD and Check_MK performed the next sync, the user login was disabled. The inverse operation was not working. Unlocking previously locked users has now been implemented correctly. Another change is, that the locking property in Check_MK is now read-only for LDAP users.

5 years, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1