CVE-2024-22037

This update fixes the following issues:

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

golang-github-prometheus-promu was updated to version 0.17.0:

• Added codesign utility function

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. …

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…

This update fixes the following issues:

scap-security-guide was updated to version 0.1.75 (jsc#ECO-3319):

• Added Ism profile for OL8, OL9
• Added new product kylinserver10
• Created OL10 product
• Release SLMicro5 product
• Replaced two date injections by SOURCE_DATE_EPOCH to make reproducible (bsc#1230361)
• Updated PCI-DSS control file for version 4.0.1

spacecmd was updated to version 5.0.11-0:

• Updated translation strings

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)

This update fixes the following issues:

salt:

• Revert setting SELinux context for minion service (bsc#1233667)
• Removed System V init support
• Fix the condition of alternatives for Tumbleweed and Leap 16
• Build all python bindings for all flavors
• Make minion reconnecting on changing master IP (bsc#1228182)
• Handle logger exception when flushing already closed file
• Include passlib as a recommended dependency
• Make Salt Bundle more tolerant to long running jobs (bsc#1228690)

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)

venv-salt-minion:

• Included D-Bus python module for SUSE distros (bsc#1231618)
• Reverted setting SELinux context for minion service (bsc#1233667)
• Make minion reconnecting on changing master IP (bsc#1228182)
• Fixed post_start_cleanup.sh shebang to work on all systems
• Handle logger exception when flushing already closed file
• Made Salt Bundle more tolerant to long running jobs (bsc#1228690)
• Modified:
  • include-rpm
  • filter-requires.sh