[//]: # (werk v2)
# Brute-force protection ineffective for some login methods
key | value
---------- | ---
date | 2024-04-09T12:24:12+00:00
version | 2.3.0b5
class | security
edition | cre
component | wato
level | 1
compatible | yes
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 _for human user accounts_.
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.
**Affected Versions**:
* 2.3.0 (beta)
* 2.2.0
* 2.1.0
* 2.0.0 (EOL)
**Mitigations**:
If updating is not possible, the brute-force attempts can be hindered by using a strong password policy.
**Vulnerability Management**:
We have rated the issue with a CVSS Score of 5.9 (Medium) with the following CVSS vector: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`
and assigned CVE `CVE-2024-28825`.
[//]: # (werk v2)
# check_httpv2: Lookup password containing whitespace
key | value
---------- | ---
date | 2024-04-16T13:05:49+00:00
version | 2.3.0b5
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Previously, the active check "HTTP web service" failed to parse the site's
password store when there was at least one stored password containing whitespaces.
This was observable when configuring "Authentication" with a password from password store,
and resulted in a *CRIT* state and an error message like
```
error: invalid value 'http_pass' for '--auth-pw-pwstore <AUTH_PW_PWSTORE>': Can't parse password store: Unexpected format.
```
in the service's summary.
[//]: # (werk v2)
# New APIs: Crash during config generation for custom special agent or active check calls
key | value
---------- | ---
date | 2024-04-15T07:19:19+00:00
version | 2.3.0b5
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This only affects plugin developers using the new API in `cmk.server_side_calls`.
The config generation for custom plugins crashed when passwords where in cluded in the command.
The mechanism how to pass `Secret`s has changed since 2.3.0b3.
To learn how to adjust your special agent or active check to the new API, please refer to the Sphinx documentation of the `cmk.server_side_calls.v1.Secret` object.
[//]: # (werk v2)
# Graph oject lists: Avoid strange help texts in list views (non-English only)
key | value
---------- | ---
date | 2024-04-15T10:20:16+00:00
version | 2.3.0b5
class | fix
edition | cee
component | multisite
level | 1
compatible | yes
When using Checkmk in a language other than English, the list views for graph collections, graph
tunings, custom graphs and forecast graphs might have displayed strange help texts such as
"Project-Id-Version: Checkmk user interface translation 0.1 ...".
This happened only for graph objects with empty descriptions and only if the inline help was
activated for the corresponding page.
[//]: # (werk v2)
# Rendering of fractional values in some few rulesets
key | value
---------- | ---
date | 2024-04-11T10:25:58+00:00
version | 2.3.0b5
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This only affects the 2.3-beta versions.
There where issues when rendering fractional values in some specific rulesets.
[//]: # (werk v2)
# check_mailboxes: Fixed handling of error "Not allowed to access Non IPM folder."
key | value
---------- | ---
date | 2024-04-12T08:34:09+00:00
version | 2.3.0b5
class | fix
edition | cre
component | packages
level | 1
compatible | yes
Due to a recent change in Microsoft 365, the access to Exchange mailbox folders via the active check `check_mailboxes` could fail with an error message like this:
```
Unhandled exception: ErrorAccessDenied('Not allowed to access Non IPM folder.')
```
With this werk we update the version of the package `exchangelib` to v5.2.1, fixing the respective error handling.
[//]: # (werk v2)
# Ruleset API: rename Dictionaries 'deprecated_elements'
key | value
---------- | ---
date | 2024-04-09T10:11:41+00:00
version | 2.3.0b5
class | feature
edition | cre
component | checks
level | 1
compatible | no
This only affects plugin developers using the new ruleset API.
The `Dictionary`s attribute `deprecated_elements` is renamed to
`ignored_elements`.
It is validated that no present elements are marked as 'ignored'.