Title: mkeventd: Forward to remote Event Console or Syslog server if configured
Class: fix
Compatible: compat
Component: notifications
Date: 1718284259
Edition: cre
Level: 1
Version: 2.2.0p28
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.
Title: Allow upload of Checkmk 2.3 compliant MKPs
Class: fix
Compatible: compat
Component: checks
Date: 1718184355
Edition: cre
Level: 1
Version: 2.2.0p28
Users where unable to upload MKPs containing files that are only relevant for Checkmk 2.3.
However, it should be possible to upload such MKPs in preperation for an upgrade.
[//]: # (werk v2)
# Rittal temperature check regression
key | value
---------- | ---
date | 2024-06-14T11:21:23+00:00
version | 2.3.0p7
class | fix
edition | cre
component | checks
level | 1
compatible | yes
You're affected if you're using rittal temperature checks under 2.3.0.
This regression exists since 2.3.0b1 and creates the following crash:
```
File "/omd/sites/YOURSITE/lib/python3/cmk/plugins/lib/temperature.py", line 319, in check_temperature
raise ValueError (Cannot compute trend. Either specify both variables 'unique_name' and 'value_store' or none.)
```
[//]: # (werk v2)
# cisco_temperature: Handle Invalid Device Readings
key | value
---------- | ---
date | 2024-06-13T12:14:09+00:00
version | 2.3.0p7
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.
[//]: # (werk v2)
# jenkins_nodes: Fix handling of multi-label nodes
key | value
---------- | ---
date | 2024-06-12T14:31:49+00:00
version | 2.3.0p7
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.3.0p7
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)
# Restart scheduler after setting "use the status of a service"
key | value
---------- | ---
date | 2024-06-13T14:21:01+00:00
version | 2.3.0p7
class | fix
edition | cee
component | core
level | 1
compatible | yes
This fixes the case where the default check scheduler would not restart after
the user temporarily set "use the status of service" as the "host check
command". The corresponding log entry was "refuse to schedule invalid jobhost
... at 1970-0101 ...".