Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

suse-cvrf логотип

SUSE-SU-2025:0525-1

Опубликовано: 14 фев. 2025
Источник: suse-cvrf

Описание

Security update for SUSE Manager Client Tools

This update fixes the following issues:

dracut-saltboot was updated to version 0.1.1728559936.c16d4fb:

  • Added MAC based terminal naming option (jsc#SUMA-314)

golang-github-prometheus-prometheus was updated from version 2.45.6 to 2.53.3 (jsc#PED-11649):

  • Security issues fixed:

    • CVE-2024-51744: Updated golang-jwt to version 5.0 to fix bad error handling (bsc#1232970)
  • Highlights of other changes:

    • Performance:
      • Significant enhancements to PromQL execution speed, TSDB operations (especially querying and compaction) and remote write operations.
      • Default GOGC value lowered to 75 for better memory management.
      • Option to limit memory usage from dropped targets added.
    • New Features:
      • Experimental OpenTelemetry ingestion.
      • Automatic memory limit handling.
      • Native histogram support, including new functions, UI enhancements, and improved scraping.
      • Improved alerting features, such as relabeling rules for AlertmanagerConfig and a new query_offset option.
      • Expanded service discovery options with added metadata and support for new services.
      • New promtool commands for PromQL formatting, label manipulation, metric pushing, and OpenMetrics dumping.
    • Bug Fixes:
      • Numerous fixes across scraping, API, TSDB, PromQL, and service discovery.
    • For a detailed list of changes consult the package changelog or https://github.com/prometheus/prometheus/compare/v2.45.6...v2.53.3

grafana was updated from version 9.5.18 to 10.4.13 (jsc#PED-11591,jsc#PED-11649):

  • Security issues fixed:

    • CVE-2024-45337: Prevent possible misuse of ServerConfig.PublicKeyCallback by upgrading golang.org/x/crypto (bsc#1234554)
    • CVE-2023-3128: Fixed authentication bypass using Azure AD OAuth (bsc#1212641)
    • CVE-2023-6152: Add email verification when updating user email (bsc#1219912)
    • CVE-2024-6837: Fixed potential data source permission escalation (bsc#1236301)
    • CVE-2024-8118: Fixed permission on external alerting rule write endpoint (bsc#1231024)
  • Potential breaking changes in version 10:

    • In panels using the extract fields transformation, where one of the extracted names collides with one of the already existing ields, the extracted field will be renamed.
    • For the existing backend mode users who have table visualization might see some inconsistencies on their panels. We have updated the table column naming. This will potentially affect field transformations and/or field overrides. To resolve this either: update transformation or field override.
    • For the existing backend mode users who have Transformations with the time field, might see their transformations are not working. Those panels that have broken transformations will fail to render. This is because we changed the field key. To resolve this either: Remove the affected panel and re-create it; Select the Time field again; Edit the time field as Time for transformation in panel.json or dashboard.json
    • The following data source permission endpoints have been removed: GET /datasources/:datasourceId/permissions POST /api/datasources/:datasourceId/permissions DELETE /datasources/:datasourceId/permissions POST /datasources/:datasourceId/enable-permissions POST /datasources/:datasourceId/disable-permissions
      • Please use the following endpoints instead: GET /api/access-control/datasources/:uid for listing data source permissions POST /api/access-control/datasources/:uid/users/:id, POST /api/access-control/datasources/:uid/teams/:id and POST /api/access-control/datasources/:uid/buildInRoles/:id for adding or removing data source permissions
    • If you are using Terraform Grafana provider to manage data source permissions, you will need to upgrade your provider.
    • For the existing backend mode users who have table visualization might see some inconsistencies on their panels. We have updated the table column naming. This will potentially affect field transformations and/or field overrides.
    • The deprecated /playlists/{uid}/dashboards API endpoint has been removed. Dashboard information can be retrieved from the /dashboard/... APIs.
    • The PUT /api/folders/:uid endpoint no more supports modifying the folder's UID
    • Removed all components for the old panel header design.
    • Please review https://grafana.com/docs/grafana/next/breaking-changes/breaking-changes-v10-3/ for more details
    • OAuth role mapping enforcement: This change impacts GitHub, Gitlab, Okta, and Generic OAuth. To avoid overriding manually set roles, enable the skip_org_role_sync option in the Grafana configuration for your OAuth provider before upgrading
    • Angular has been deprecated
    • Grafana legacy alerting has been deprecated
    • API keys are migrating to service accounts
    • The experimental “dashboard previews” feature is removed
    • Usernames are now case-insensitive by default
    • Grafana OAuth integrations do not work anymore with email lookups
    • The “Alias” field in the CloudWatch data source is removed
    • Athena data source plugin must be updated to version >=2.9.3
    • Redshift data source plugin must be updated to version >=1.8.3
    • DoiT International BigQuery plugin no longer supported
    • Please review https://grafana.com/docs/grafana/next/breaking-changes/breaking-changes-v10-0 for more details
  • This update brings many new features, enhancements and fixes highlighted at:

spacecmd was updated to version 5.0.11-0:

  • Updated translation strings

supportutils-plugin-salt was updated to version 1.2.3:

  • Adjusted requirements for plugin to allow compatibility with supportutils 3.2.9 release (bsc#1235145)
  • Provide backwards-compatible scripts version

supportutils-plugin-susemanager-client was updated to version 5.0.4-0:

  • Adjusted requirements for plugin to allow compatibility with supportutils 3.2.9 release (bsc#1235145)

uyuni-tools was updated from version 0.1.23-0 to 0.1.27-0:

  • Security issues fixed:
    • CVE-2024-22037: Use podman secret to store the database credentials (bsc#1231497)
  • Other changes and bugs fixed:
    • Version 0.1.27-0
      • Bump the default image tag to 5.0.3
      • IsInstalled function fix
      • Run systemctl daemon-reload after changing the container image config (bsc#1233279)
      • Coco-replicas-upgrade
      • Persist search server indexes (bsc#1231759)
      • Sync deletes files during migration (bsc#1233660)
      • Ignore coco and hub images when applying PTF if they are not ailable (bsc#1229079)
      • Add --registry back to mgrpxy (bsc#1233202)
      • Only add java.hostname on migrated server if not present
      • Consider the configuration file to detect the coco or hub api images should be pulled (bsc#1229104)
      • Only raise an error if cloudguestregistryauth fails for PAYG (bsc#1233630)
      • Add registry.suse.com login to mgradm upgrade podman list (bsc#1234123)
    • Version 0.1.26-0
      • Ignore all zypper caches during migration (bsc#1232769)
      • Use the uyuni network for all podman containers (bsc#1232817)
    • Version 0.1.25-0
      • Don't migrate enabled systemd services, recreate them (bsc#1232575)
    • Version 0.1.24-0
      • Redact JSESSIONID and pxt-session-cookie values from logs and console output (bsc#1231568)

Список пакетов

SUSE Enterprise Storage 7.1
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise Module for Basesystem 15 SP6
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise Module for Package Hub 15 SP6
golang-github-prometheus-promu-0.17.0-150000.3.24.1
SUSE Linux Enterprise Server 15 SP3-LTSS
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise Server 15 SP4-LTSS
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise Server 15 SP5-LTSS
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise Server for SAP Applications 15 SP3
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise Server for SAP Applications 15 SP4
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise Server for SAP Applications 15 SP5
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Manager Client Tools 15
dracut-saltboot-0.1.1728559936.c16d4fb-150000.1.56.1
firewalld-prometheus-config-0.1-150000.3.59.1
golang-github-prometheus-prometheus-2.53.3-150000.3.59.1
grafana-10.4.13-150000.1.66.1
mgrctl-0.1.28-150000.1.16.1
mgrctl-bash-completion-0.1.28-150000.1.16.1
mgrctl-lang-0.1.28-150000.1.16.1
mgrctl-zsh-completion-0.1.28-150000.1.16.1
spacecmd-5.0.11-150000.3.130.1
supportutils-plugin-salt-1.2.3-150000.3.16.1
supportutils-plugin-susemanager-client-5.0.4-150000.3.27.1
SUSE Manager Client Tools for SLE Micro 5
dracut-saltboot-0.1.1728559936.c16d4fb-150000.1.56.1
mgrctl-0.1.28-150000.1.16.1
mgrctl-bash-completion-0.1.28-150000.1.16.1
mgrctl-lang-0.1.28-150000.1.16.1
mgrctl-zsh-completion-0.1.28-150000.1.16.1
SUSE Manager Proxy 4.3
supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Manager Server 4.3
supportutils-plugin-salt-1.2.3-150000.3.16.1
openSUSE Leap 15.6
dracut-saltboot-0.1.1728559936.c16d4fb-150000.1.56.1
golang-github-prometheus-promu-0.17.0-150000.3.24.1
spacecmd-5.0.11-150000.3.130.1
supportutils-plugin-salt-1.2.3-150000.3.16.1
supportutils-plugin-susemanager-client-5.0.4-150000.3.27.1

Описание

Grafana is validating Azure AD accounts based on the email claim. On Azure AD, the profile email field is not unique and can be easily modified. This leads to account takeover and authentication bypass when Azure AD OAuth is configured with a multi-tenant app.


Затронутые продукты
SUSE Enterprise Storage 7.1:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1

Ссылки

Описание

A user changing their email after signing up and verifying it can change it without verification in profile settings. The configuration option "verify_email_enabled" will only validate email only on sign up.


Затронутые продукты
SUSE Enterprise Storage 7.1:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1

Ссылки

Описание

The uyuni-server-attestation systemd service needs a database_password environment variable. This file has 640 permission, and cannot be shown users, but the environment is still exposed by systemd to non-privileged users.


Затронутые продукты
SUSE Enterprise Storage 7.1:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1

Ссылки

Описание

Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/cry...@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.


Затронутые продукты
SUSE Enterprise Storage 7.1:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1

Ссылки

Описание

golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.


Затронутые продукты
SUSE Enterprise Storage 7.1:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1

Ссылки

Описание

** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided.


Затронутые продукты
SUSE Enterprise Storage 7.1:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1

Ссылки

Описание

In Grafana, the wrong permission is applied to the alert rule write API endpoint, allowing users with permission to write external alert instances to also write alert rules.


Затронутые продукты
SUSE Enterprise Storage 7.1:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:supportutils-plugin-salt-1.2.3-150000.3.16.1
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS:supportutils-plugin-salt-1.2.3-150000.3.16.1

Ссылки
Уязвимость SUSE-SU-2025:0525-1