[//]: # (werk v2)
# Fixed bug during activating changes if the main versions differed between central and remote site
key | value
---------- | ---
date | 2024-07-19T09:59:43+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
The following error message was displayed during the activation of changes if the remote site had a newer major version than the central site.
```
cmk.utils.exceptions.MKGeneralException: Configuration update failed
ERROR: The Checkmk site is still running. Please stop the site before updating the configuration.
You can stop the site using 'omd stop'.". Please note that the site configuration has been synchronized partially.
```
[//]: # (werk v2)
# kube_pod_conditions: Fix Incorrectly Reported Duration of PodCondition
key | value
---------- | ---
date | 2024-07-22T16:25:44+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This problem affected users of the Kubernetes monitoring. Previously, the duration of a PodCondition
would sometimes be reported incorrectly. This affected PodConditions, for which no data was provided
by the Kubernetes API. The check would incorrectly report the duration of the previous PodCondition
instead. This has been fixed.
[//]: # (werk v2)
# Add support for MariaDB 11
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-06-10T07:54:55+00:00
level | 1
class | fix
component | checks
edition | cre
MariaDB 11 deprecated mysql* binaries and shows an error message like:
```
mysqladmin: Deprecated program name. It will be removed in a future release, use ‘/usr/bin/mariadb-admin’ instead
```
The agent plugin now checks if the MariaDB binaries are available and prefers them over the mySQL binaries.
Title: Livestatus injection in mknotifyd
Class: security
Compatible: compat
Component: notifications
Date: 1720439889
Edition: cee
Level: 1
Version: 2.1.0p47
Before this Werk a malicious notification sent via mknotifyd could allow an attacker to send arbitrary livestatus commands.
With this Werk livestatus escaping was added to the relevant functions.
This issue was found during internal review.
<em>Affected Versions</em>:
LI: 2.3.0
LI: 2.2.0
LI: 2.1.0
LI: 2.0.0 (EOL)
<em>Vulnerability Management</em>:
We have rated the issue with a CVSS Score of 6.5 Medium (<code>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L</code>) and assigned <code>CVE-2024-6542</code>.
Title: mk_filestats: Do not compute file statistics in case of a folder
Class: fix
Compatible: compat
Component: checks
Date: 1721111293
Edition: cre
Level: 1
Version: 2.2.0p32
[//]: # (werk v2)
# discovery: Update discovered parameters
key | value
---------- | ---
date | 2024-07-19T15:01:34+00:00
version | 2.3.0p11
class | fix
edition | cre
component | checks
level | 1
compatible | yes
With the rework of `Bulk discovery` and `Periodic service discovery` in 2.3,
discovered parameters weren't updated anymore if `Refresh all services and host labels (tabula rasa)`
option was used.
With this werk, tabula rasa option works like in the version 2.2.
[//]: # (werk v2)
# mk_filestats: Do not compute file statistics in case of a folder
key | value
---------- | ---
compatible | yes
version | 2.3.0p11
date | 2024-07-16T06:28:13+00:00
level | 1
class | fix
component | checks
edition | cre