Title: ldap: show the correct customer for ldap users
Class: fix
Compatible: compat
Component: wato
Date: 1713448991
Edition: cme
Level: 1
Version: 2.2.0p25
When an ldap connection is configured for a specific customer, this
wasn't reflected in the users for that ldap connection. This werk
addresses this issue by now showing the correct customer.
Title: Brute-force protection ineffective for some login methods
Class: security
Compatible: compat
Component: wato
Date: 1712665452
Edition: cre
Level: 1
Version: 2.2.0p25
Prior to this Werk, the mechanism to lock user accounts after too many failed login attempts was only effective for the web form login method.
Login attempts via the REST API and basic authentication did not count towards the lockout mechanism.
As a result, an attacker could try to brute-force user passwords without triggering the lockout mechanism.
This Werk adds the same locking mechanism to login via the REST API and basic authentication <em>for human user accounts</em>.
Note that automation accounts are remain unaffected by the lockout mechanism to avoid having them locked by malicious intent.
It is therefore important to use long, random automation secrets.
This issue was found during internal review.
<strong>Affected Versions</strong>:
LI: 2.3.0 (beta)
LI: 2.2.0
LI: 2.1.0
LI: 2.0.0 (EOL)
<strong>Mitigations</strong>:
If updating is not possible, the brute-force attempts can be hindered by using a strong password policy.
<strong>Vulnerability Management</strong>:
We have rated the issue with a CVSS Score of 5.9 (Medium) with the following CVSS vector: <code>CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N</code>
and assigned CVE <code>CVE-2024-28825</code>.
[//]: # (werk v2)
# Check certificates: Fix checking of common name of issuer
key | value
---------- | ---
date | 2024-04-18T11:02:41+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The active certificate check (configured via the ruleset *Check certificates*) did not check the
common name (CN) of the certificate issuer correctly:
* If only the checking of the issuer CN was activated, the CN of the subject was checked instead.
* If both the checking of the issuer and the subject CN where activated, the active check crashed with\
<code>error: the argument '--subject-cn \<SUBJECT_CN\>' cannot be used multiple times.</code>
[//]: # (werk v2)
# omd start redis: Don't Start If Process Already Running
key | value
---------- | ---
date | 2024-04-18T16:06:48+00:00
version | 2.4.0b1
class | fix
edition | cre
component | omd
level | 1
compatible | yes
With this Werk, `omd start` will no longer create a new redis process if redis is already started.
This aligns the behaviour with the other services of a site.
[//]: # (werk v2)
# Linux agent: drop support for FreeIPMI 0.8.0 and earlier
key | value
---------- | ---
date | 2024-04-17T20:21:00+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | no
This change is only incompatible for users monitoring hosts with a FreeIPMI
version of 0.8.0 or earlier.
FreeIPMI 0.8.1 was released in December 2009.
[//]: # (werk v2)
# Logfile pattern analyzer: Fix crash for first rule without regex pattern
key | value
---------- | ---
date | 2024-04-17T08:10:14+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The "Logfile pattern analyzer" page crashed when the first "Logfile pattern" rule in place did not hold a regex pattern and a later rule did hold a regex pattern.
The rendering of the table of rules would crash with
```
Internal error: list index out of range
```
This is fixed and all rules are rendered as expected.
[//]: # (werk v2)
# Licensing: Reset license state when updating from Enterprise to non-Enterprise
key | value
---------- | ---
date | 2024-04-17T16:10:14+00:00
version | 2.4.0b1
class | fix
edition | cee
component | setup
level | 1
compatible | no
When upgrading from an Enterprise to another edition is performed, the site will start a new trial period, even if licensing credentials had already been configured.
To license the product, a license verification needs to be performed (on the licensing page: Setup > Maintenance > Licensing > Online/Offline verification).
[//]: # (werk v2)
# Support Diagnostics: The timeout for creating a dump is now configurable
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-04-12T11:07:00+00:00
level | 1
class | feature
component | wato
edition | cre
Before this werk, the process of creating a Support Diagnostics Dump sometimes lead to a timeout exception. The hard-coded timeout was 110s.
Now, it's possible to configure the timeout in the user interface.
[//]: # (werk v2)
# ldap: show the correct customer for ldap users
key | value
---------- | ---
date | 2024-04-18T14:03:11+00:00
version | 2.4.0b1
class | fix
edition | cme
component | wato
level | 1
compatible | yes
When an ldap connection is configured for a specific customer, this
wasn't reflected in the users for that ldap connection. This werk
addresses this issue by now showing the correct customer.
Title: mk_oracle: fix two parse errors
Class: fix
Compatible: compat
Component: checks
Date: 1712642491
Edition: cre
Level: 1
Version: 2.1.0p42
Due to fixes introduced with
<a href="https://checkmk.com/werk/16232">Werk #16232</a> new error messages
have been introduced to sections which previously had not to handle any errors.
Now <tt>oracle_processes</tt> and <tt>oracle_recovery_area</tt> services can
handle the new error messages.