Werk 16116 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Fixed association of contacts with hosts/services/contactgroups
key | value
---------- | ---
date | 2024-04-05T13:48:37+00:00
version | 2.3.0b4
class | fix
edition | cre
component | livestatus
level | 3
compatible | yes
Checkmk 2.3 beta introduced a regression regarding contacts when
then Nagios core was used: The association of contacts with hosts,
services and contact groups was incorrect. A symptom of this bug
were e.g. missing hosts or services in the GUI.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Fixed association of contacts with hosts/services/contactgroups
key | value
---------- | ---
date | 2024-04-05T13:48:37+00:00
- version | 2.3.0b5
? ^
+ version | 2.3.0b4
? ^
class | fix
edition | cre
component | livestatus
level | 3
compatible | yes
Checkmk 2.3 beta introduced a regression regarding contacts when
then Nagios core was used: The association of contacts with hosts,
services and contact groups was incorrect. A symptom of this bug
were e.g. missing hosts or services in the GUI.
Werk 15515 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# check_http: Soft deprecatation of old HTTP monitoring plug-in
key | value
---------- | ---
date | 2024-04-03T13:15:48+00:00
version | 2.3.0b4
class | feature
edition | cre
component | checks
level | 2
compatible | no
The old plug-in is being deprecated in a soft way with this werk. Unlike
hard deprecation, the deprecated rule set "Check HTTP service" will remain
fully functional. However, new rules should only be created if absolutely
necessary, such as when experiencing issues with the new "Check HTTP web
service" implementation and needing to roll back to the old one.
Please note that the rule set will be hard deprecated in version 2.4.0,
meaning that you will no longer be able to create new rules. However, the
plug-in itself will remain available as this is a component of the
monitoring-plugins collection that comes with Checkmk.
Please let us know if you find any features that were present in the old
plug-in but are missing in the new one.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# check_http: Soft deprecatation of old HTTP monitoring plug-in
key | value
---------- | ---
date | 2024-04-03T13:15:48+00:00
version | 2.3.0b4
class | feature
edition | cre
component | checks
level | 2
compatible | no
The old plug-in is being deprecated in a soft way with this werk. Unlike
hard deprecation, the deprecated rule set "Check HTTP service" will remain
fully functional. However, new rules should only be created if absolutely
necessary, such as when experiencing issues with the new "Check HTTP web
service" implementation and needing to roll back to the old one.
Please note that the rule set will be hard deprecated in version 2.4.0,
meaning that you will no longer be able to create new rules. However, the
plug-in itself will remain available as this is a component of the
monitoring-plugins collection that comes with Checkmk.
- Please know us know if you find any features that were present in the old
? --------
+ Please let us know if you find any features that were present in the old
? +++++++
plug-in but are missing in the new one.
[//]: # (werk v2)
# check_cert: New active check for advanced certificate monitoring
key | value
---------- | ---
date | 2024-04-03T13:42:35+00:00
version | 2.3.0b4
class | feature
edition | cre
component | checks
level | 2
compatible | yes
The _check_http_ plug-in was previously the only method to monitor
certificates out-of-the-box with Checkmk. With the new plug-in Checkmk
provides an extensive functionality to monitor certificates. This includes
but is not limited to certificates provided by the HTTP protocol.
With the new plug-in you can monitor all certificates provided through
a TCP connection to encrypt communication. This includes the monitoring
of
* validity times (max and remaining)
* issuer fields
* subject fields
* encryption algorithm
* alternative names
* response times
* public key algorithm and size
* serial number
As with the reworked plugin to monitor web services, you are able to
configure multiple services within a single rule.
[//]: # (werk v2)
# check_http: Soft deprecatation of old HTTP monitoring plug-in
key | value
---------- | ---
date | 2024-04-03T13:15:48+00:00
version | 2.3.0b4
class | feature
edition | cre
component | checks
level | 2
compatible | no
The old plug-in is being deprecated in a soft way with this werk. Unlike
hard deprecation, the deprecated rule set "Check HTTP service" will remain
fully functional. However, new rules should only be created if absolutely
necessary, such as when experiencing issues with the new "Check HTTP web
service" implementation and needing to roll back to the old one.
Please note that the rule set will be hard deprecated in version 2.4.0,
meaning that you will no longer be able to create new rules. However, the
plug-in itself will remain available as this is a component of the
monitoring-plugins collection that comes with Checkmk.
Please know us know if you find any features that were present in the old
plug-in but are missing in the new one.
[//]: # (werk v2)
# mk_oracle(ps1): Follow-up to privilege escalation fix
key | value
---------- | ---
compatible | no
version | 2.3.0b5
date | 2024-04-05T11:02:27+00:00
level | 2
class | fix
component | checks
edition | cre
You might be affected by this Werk if you use <tt>mk_oracle</tt> on Windows.
Werk <a href="https://checkmk.com/werk/16232">Werk #16232</a> introduced a
regression, thereby disrupting Oracle monitoring on Windows.
This Werk addresses above mentioned issue that affects versions 2.1.0p41,
2.2.0p24, and 2.3.0b4.
Since this release, Oracle monitoring on Windows is fully supported under
condition you use an account without administrator rights or the certain
executable binaries, <tt>sqlplus.exe</tt>, <tt>tnsping.exe</tt> and, if
presented, <tt>crsctl.exe</tt> are write-protected, with the possible
exception being the Administrator.
If you are unable or prefer not to use an unprivileged account then you may
need to adjust permissions for above mentioned binaries: remove <tt>Write</tt>,
<tt>Full Control</tt> and <tt>Modify</tt> permissions for any non-Administrator
user and group.
More information about can be found at <a href="https://checkmk.atlassian.net/wiki/x/AQA1B">here</a>.
[//]: # (werk v2)
# Fixed association of contacts with hosts/services/contactgroups
key | value
---------- | ---
date | 2024-04-05T13:48:37+00:00
version | 2.3.0b5
class | fix
edition | cre
component | livestatus
level | 3
compatible | yes
Checkmk 2.3 beta introduced a regression regarding contacts when
then Nagios core was used: The association of contacts with hosts,
services and contact groups was incorrect. A symptom of this bug
were e.g. missing hosts or services in the GUI.
[//]: # (werk v2)
# Enhanced MS SQL Server monitoring
key | value
---------- | ---
date | 2024-04-03T07:47:56+00:00
version | 2.3.0b4
class | feature
edition | cre
component | checks
level | 2
compatible | yes
With this release MS SQL Server is monitored using new plugin and new GUI.
The old plugin is still supported but are considered deprecated.
Key Enhancements out-of-the-box:
- Configuration flexibility: The plugin can be configured through a YAML config file for any edition and/or a graphical user interface (GUI) for enterprise edition or better.
- Cross platform: The plugin can be deployed on Linux and Windows.
- Enhanced monitoring capabilities: Supports monitoring of remote databases on both Linux and Windows hosts, in addition to local monitoring on Windows hosts.
- Customizable monitoring sections: Sections are now selectable and configurable
- Customizable SQL statements: you may change SQL statement either manually(place file in `mssql` sub directory in config dir) or using `Custom files` rule in GUI.
- Multi-instance support: Enables the selection of different instances for monitoring. Every instance can be configured separately
- Multi-host support: possible to monitor databases on various hosts using one deployed plugin.
- Security enhancements: Limited support for certificates is now available.
- Asynchronous operation: Any section with exception `instances` can be set up for asynchronous operation.
- Piggyback: It's possible to direct the output of a plugin to a different host, rather than to the host that retrieves the data.
- Other improvements:
- Automatic detection of instances is possible for any Windows host, local and remote, depending on SQL Server Setup.
- Full logging support including rotation and file limits
- Limit for maximal connection counts
- Cache time and timeout can be configured too
[//]: # (werk v2)
# The configuration is correctly loaded by RRD helper processes
key | value
---------- | ---
date | 2024-03-26T10:03:03+00:00
version | 2.3.0b4
class | fix
edition | cee
component | core
level | 2
compatible | yes
This change ensures the reloading of the configuration by already
running RRD processes, thereby guaranteeing that those processes are
using the correct configuration.
SUP-17787
CMK-16318
[//]: # (werk v2)
# Rename service labels for Robotmk
key | value
---------- | ---
date | 2024-03-25T12:28:56+00:00
version | 2.3.0b4
class | feature
edition | cee
component | multisite
level | 2
compatible | yes
This is a follow-up for werk #13872.
The service labels have been renamed to 'cmk/rmk/html_last_log:yes' and 'cmk/rmk/html_last_error_log:yes'.
The icons for the last log file and last error log file will have an icon based on the new labels as well as the old ones from werk #13872.
[//]: # (werk v2)
# mk_oracle(ps1): Prevent privilege esclation to root
key | value
---------- | ---
compatible | yes
version | 2.3.0b4
date | 2024-01-17T08:20:43+00:00
level | 3
class | security
component | checks
edition | cre
The agent plugins mk_oracle, mk_oracle.ps1 and mk_oracle_crs were vulnerable to privilege escalation to root by the oracle user.
A malicious oracle user could replace a binary (e.g. sqlplus) with another script and put
it in the corresponding directory. The script would be executed by the root user.
All binaries, which are called by the plugins, are now checked if they need to be executed as a non-root (non-administrator under Windows) user, preventing the privilege escalation.
Affected binaries are: sqlplus, tnsping, crsctl.
<h3>Affected Versions</h3>
* 2.3.0 (beta)
* 2.2.0
* 2.1.0
* 2.0.0 (EOL) and older
<h3>Mitigations</h3>
If updating is not possible, disable the mk_oracle plugin.
<h3>Vulnerability Management</h3>
We have rated the issue with a CVSS score of 8.2 (High) with the following CVSS vector:
<code>CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H</code>
We have assigned <code>CVE-2024-0638</code>.
<h3>Changes</h3>
All called binaries are now executed in a safe way.