[//]: # (werk v2)
# mkeventd: Forward to remote Event Console or Syslog server if configured
key | value
---------- | ---
compatible | yes
version | 2.3.0p7
date | 2024-06-13T13:10:59+00:00
level | 1
class | fix
component | notifications
edition | cre
The notification method "Forward notification to Event Console" offers the
option to forward messages to a remote Event Console or Syslog server.
In earlier versions the messages were only forwarded if the local Event Console
(mkeventd) was not running.
This has been fixed.
[//]: # (werk v2)
# Fix checkmk errors appearing at the bottom of the page
key | value
---------- | ---
compatible | yes
version | 2.3.0p7
date | 2024-05-28T16:05:26+00:00
level | 1
class | fix
component | wato
edition | cre
A certain class of errors, including time out errors appeared at
the bottom of a page, making the error difficult to notice, especially
when viewing large tables. With this werk, these error messages
will appear on top of the page like all other errors.
[//]: # (werk v2)
# Test notifications: Match labels for hosts on remote sites
key | value
---------- | ---
date | 2024-06-11T17:19:29+00:00
version | 2.3.0p7
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
Labels of hosts from remote sites were not added to the notification context.
This results in no match on testing a label condition, even the host had the
label configured.
Hosts on the central site were not affected.
[//]: # (werk v2)
# parent scan: Deprecate command line tool in favor of REST API endpoint
key | value
---------- | ---
date | 2024-05-02T07:43:39+00:00
version | 2.3.0p7
class | feature
edition | cre
component | wato
level | 1
compatible | no
In this werk, we replace the `cmk --scan-parents` command line tool with
a more flexible parent scan REST API endpoint.
As opposed to the command line option, the new endpoint will no longer
create automatically-applied `parents.mk` config files but rely on the
standard WATO configuration mechanism, so changes need to be activated
afterwards.
**Attention: Incompatibility, possible data loss in distributed
monitoring setups**
If you have previously used the parent scan through the command line
tool, the resulting `parents.mk` config files will be migrated into your
hosts configuration during the update process. However, **only parent
scan configurations on the central site will be migrated**, remote
site `parents.mk` configuration files will just be ignored. If this
affects your setup, please re-trigger a parent scan for the affected
child hosts in the GUI or REST API.
[//]: # (werk v2)
# Don't escape customer name
key | value
---------- | ---
compatible | yes
version | 2.3.0p7
date | 2024-06-10T15:18:56+00:00
level | 1
class | fix
component | wato
edition | cme
If you created a customer with e.g. an ampersand in the customer name, the name
was escaped on the customers page showing "&" instead of "&".
[//]: # (werk v2)
# jenkins_nodes: Fix handling of multi-label nodes
key | value
---------- | ---
date | 2024-06-12T14:31:49+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
When using the Jenkins node check in an environment that had multiple labels assigned to a build node, the detection of busy and idle executors and the mode had been wrong.
This werk fixes the way this data is obtained and should produce the expected values.
[//]: # (werk v2)
# XSS in inventory tree
key | value
---------- | ---
date | 2024-06-07T07:20:37+00:00
version | 2.4.0b1
class | security
edition | cre
component | inv
level | 1
compatible | yes
Prior to this Werk an attacker with control over an agent was able to inject HTML in the output which was then rendered in the inventory tree of the coresponding host.
This problem exists only if the rule *Do hardware/software inventory* is set for the compromised agent/host.
We found this vulnerability internally.
**Affected Versions:**
* 2.3.0
* 2.2.0
* 2.1.0
* 2.0.0
**Mitigations**:
If you are unable to patch you can disable inventory scanning for all hosts.
**Indicators of Compromise:**
You can check `var/check_mk/inventory/` for inventories with embedded HTML.
This only indicates current 'attacks'.
Previous attacks (where the agent does not output the payload anymore) are not discoverable after some time (caching).
**Vulnerability Management:**
We have rated the issue with a CVSS Score of 6.5 (Medium) with the following CVSS vector:
`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`
We assigned CVE-2024-5741 to this vulnerability.
**Changes:**
This Werk adds sanitation to the HTML output.
[//]: # (werk v2)
# cisco_temperature: Handle Invalid Device Readings
key | value
---------- | ---
date | 2024-06-13T12:14:09+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Cisco SNMP devices may report temperatures of "inf" or "-inf". According to
CISCO-ENTITY-SENSOR-MIB, these values are not valid.
Previously, Checkmk would treat non-finite temperatures as valid. This invalid
data would be written to `tmp/check_mk/counters/`, which then caused the
`Check_MK` service to become UNKNOWN. Furthermore, the services on the host
would become stale. With this Werk, the problematic values not persisted. Only
the affected service state will be UNKNOWN.
If you are affected, you can delete the corrupted counter file in
`tmp/check_mk/counters/<host name>`. To fix the readings reported by your
device, please directly contact Cisco.