File _patchinfo of Package patchinfo.28934

Overview Repositories Revisions Requests Users Attributes Meta

File _patchinfo of Package patchinfo.28934

<patchinfo incident="28934">
  <rating>important</rating>
  <packager>deneb_alpha</packager>
  <category>security</category>
  <summary>Security update for SUSE Manager Client Tools</summary>
  <description>This update fixes the following issues:

bind:

- Provide bind dependencies and solve installation issues on SUSE Linux Enterprise Micro
- There are no source changes    
    
dracut-saltboot:

- Update to version 0.1.1681904360.84ef141 
  * Load network configuration even when missing protocol version (bsc#1210640)

grafana:
    
- Version update from 8.5.22 to 9.5.1 (jsc#PED-3694):
  * Security fixes:
    - CVE-2023-1410: grafana: Stored XSS in Graphite FunctionDescription tooltip (bsc#1209645)
    - CVE-2023-1387: grafana: JWT URL-login flow leaks token to data sources through request parameter in proxy requests
      (bnc#1210907)
    - CVE-2022-36062: grafana: Fix RBAC folders/dashboards privilege escalation (bsc#1203596)
    - CVE-2022-35957: grafana: Escalation from admin to server admin when auth proxy is used (bsc#1203597)
    - CVE-2022-32149: Upgrade x/text to version unaffected by CVE-2022-32149 (bsc#1204501)
    - CVE-2022-31107: grafana: OAuth account takeover (bsc#1201539)
    - CVE-2022-31097: grafana: stored XSS vulnerability (bsc#1201535)
    - CVE-2022-27664: go1.18,go1.19: net/http: handle server errors after sending GOAWAY (bsc#1203185)
    - CVE-2022-0155: follow-redirects: Exposure of Private Personal Information to an Unauthorized Actor
    - CVE-2021-43138: spacewalk-web: a malicious user can obtain privileges via the mapValues() method(bsc#1200480)
    - CVE-2021-3918: json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes
      ('Prototype Pollution') (bsc#1192696)
    - CVE-2021-3807: node-ansi-regex: Inefficient Regular Expression Complexity in chalk/ansi-regex (bsc#1192154)
    - CVE-2020-7753: nodejs-trim: Regular Expression Denial of Service (ReDoS) in trim function 
  * Important changes:
    - Default named retention policies won't be used to query.
      Users who have a default named retention policy in their influxdb database, have to rename it to something else.
      To change the hardcoded retention policy in the dashboard.json, users must then select the right retention policy
      from dropdown and save the panel/dashboard.
    - Grafana Alerting rules with NoDataState configuration set to Alerting will now respect "For" duration.
    - Users who use LDAP role sync to only sync Viewer, Editor and Admin roles, but grant Grafana Server Admin role
      manually will not be able to do that anymore. After this change, LDAP role sync will override any manual changes
      to Grafana Server Admin role assignments. If grafana_admin is left unset in LDAP role mapping configuration, it
      will default to false.
    - The InfluxDB backend migration feature toggle (influxdbBackendMigration) has been reintroduced in this version
      as issues were discovered with backend processing of InfluxDB data. Unless this feature toggle is enabled, all
      InfluxDB data will be parsed in the frontend. This frontend processing is the default behavior. 
      In Grafana 9.4.4, InfluxDB data parsing started to be handled in the backend. If you have upgraded to 9.4.4
      and then added new transformations on InfluxDB data, those panels will fail to render. To resolve this either:
      Remove the affected panel and re-create it or edit the `time` field as `Time` in `panel.json` 
      or `dashboard.json`
    - The `@grafana/ui` package helper function `selectOptionInTest` used in frontend tests has been removed as it
      caused testing libraries to be bundled in the production code of Grafana. If you were using this helper function
      in your tests please update your code accordingly.
    - Removed deprecated `checkHealth` prop from the `@grafana/e2e` `addDataSource` configuration. Previously this
      value defaulted to `false`, and has not been used in end-to-end tests since Grafana 8.0.3.
    - Removed the deprecated `LegacyBaseMap`, `LegacyValueMapping`, `LegacyValueMap`, and `LegacyRangeMap` types, and
      `getMappedValue` function from grafana-data. See the documentation for the migration.
      This change fixes a bug in Grafana where intermittent failure of database, network between Grafana and the
      database, or error in querying the database would cause all alert rules to be unscheduled in Grafana. 
      Following this change scheduled alert rules are not updated unless the query is successful.
    - The `get_alert_rules_duration_seconds` metric has been renamed to `schedule_query_alert_rules_duration_seconds`
    - Any secret (data sources credential, alert manager credential, etc, etc) created or modified with Grafana v9.0
      won't be decryptable from any previous version (by default) because the way encrypted secrets are stored into the
      database has changed. Although secrets created or modified with previous versions will still be decryptable by
      Grafana v9.0.
    - If required, although generally discouraged, the `disableEnvelopeEncryption` feature toggle can be enabled to
      keep envelope encryption disabled once updating to Grafana
    - In case of need to rollback to an earlier version of Grafana (i.e. Grafana v8.x) for any reason, after being
      created or modified any secret with Grafana v9.0, the `envelopeEncryption` feature toggle will need to be enabled
      to keep backwards compatibility (only from `v8.3.x` a bit unstable, from `8.5.x` stable).
    - As a final attempt to deal with issues related with the aforementioned situations, the 
      `grafana-cli admin secrets-migration rollback` command has been designed to move back all the Grafana secrets
      encrypted with envelope encryption to legacy encryption. So, after running that command it should be safe to
      disable envelope encryption and/or roll back to a previous version of Grafana.
      Alternatively or complementarily to all the points above, backing up the Grafana database before updating could
      be a good idea to prevent disasters (although the risk of getting some secrets corrupted only applies to those 
      updates/created with after updating to Grafana v9.0).
    - In Elasticsearch, browser access mode was deprecated in grafana 7.4.0 and removed in 9.0.0. If you used this mode
      please switch to server access mode on the datasource configuration page.
    - Environment variables passed from Grafana to external Azure plugins have been renamed:
      `AZURE_CLOUD` renamed to `GFAZPL_AZURE_CLOUD`,
      `AZURE_MANAGED_IDENTITY_ENABLED` renamed to `GFAZPL_MANAGED_IDENTITY_ENABLED`,
      `AZURE_MANAGED_IDENTITY_CLIENT_ID` renamed to `GFAZPL_MANAGED_IDENTITY_CLIENT_ID`.
      There are no known plugins which were relying on these variables. Moving forward plugins should read Azure
      settings only via Grafana Azure SDK which properly handles old and new environment variables.
    - Removes support for for ElasticSearch versions after their end-of-life, currently versions &lt; 7.10.0.
      To continue to use ElasticSearch data source, upgrade ElasticSearch to version 7.10.0+.
    - Application Insights and Insight Analytics queries in Azure Monitor were deprecated in Grafana 8.0 and finally
      removed in 9.0. Deprecated queries will no longer be executed.
    - grafana/ui: Button now specifies a default type="button".
      The `Button` component provided by @grafana/ui now specifies a default `type="button"` when no type is provided.
      In previous versions, if the attribute was not specified for buttons associated with a `&lt;form&gt;` the
      default value was `submit` per the specification. You can preserve the old behavior by explicitly setting the
      type attribute: `&lt;Button type="submit" /&gt;`
    - The `Rename by regex` transformation has been improved to allow global patterns of the form 
      `/&lt;stringToReplace&gt;/g`.
      Depending on the regex match used, this may cause some transformations to behave slightly differently. You can
      guarantee the same behaviour as before by wrapping the `match` string in forward slashes (`/`), e.g. `(.*)` would
      become `/(.*)/`
    - `&lt;Select /&gt;` menus will now portal to the document body by default. This is to give more consistent
      behaviour when positioning and overlaying. If you were setting`menuShouldPortal={true}` before you can safely 
      remove that prop and behaviour will be the same. If you weren't explicitly setting that prop, there should be no
      visible changes in behaviour but your tests may need updating. If you were setting `menuShouldPortal={false}`
      this will continue to prevent the menu from portalling.
    - Grafana alerting endpoint prefixed with `api/v1/rule/test` that tests a rule against a Corte/Loki data source now
      expects the data source UID as a path parameter instead of the data source numeric identifier.
    - Grafana alerting endpoints prefixed with `api/prometheus/` that proxy requests to a Cortex/Loki data source now
      expect the data source UID as a path parameter instead of the data source numeric identifier.
    - Grafana alerting endpoints prefixed with `api/ruler/` that proxy requests to a Cortex/Loki data source now expect
      the data source UID as a path parameter instead of the data
    - Grafana alerting endpoints prefixed with `api/alertmanager/` that proxy requests to an Alertmanager now expect
      the data source UID as a path parameter instead of the data source numeric identifier.
    - The format of log messages have been updated, `lvl` is now `level` and `eror`and `dbug` has been replaced with
      `error` and `debug`. The precision of timestamps has been increased.
      To smooth the transition, it is possible to opt-out of the new log format by enabling the feature toggle
      `oldlog`.
      This option will be removed in a future minor release.
    - In the Loki data source, the dataframe format used to represent Loki logs-data has been changed to a more
      efficient format. The query-result is represented by a single dataframe with a "labels" column, instead of the
      separate dataframes for every labels-value. When displaying such data in explore, or in a logs-panel in the
      dashboard will continue to work without changes, but if the data was loaded into a different dashboard-panel, or
      Transforms were used, adjustments may be necessary. For example, if you used the "labels to fields" 
      transformation with the logs data, please switch to the "extract fields" transformation.
  * Deprecations:
    - The `grafana_database_conn_*` metrics are deprecated, and will be removed in a future version of Grafana. Use 
      the `go_sql_stats_*` metrics instead.
    - Support for compact Explore URLs is deprecated and will be removed in a future release. Until then, when
      navigating to Explore using the deprecated format the URLs are automatically converted. If you have
      existing links pointing to Explore update them using the format generated by Explore upon navigation.
      You can identify a compact URL by its format. Compact URLs have the left (and optionally right) url parameter as
      an array of strings, for example `&amp;left=["now-1h","now"...]`. The standard explore URLs follow a key/value
      pattern, for example `&amp;left={"datasource":"test"...}`. Please be sure to check your dashboards for any
      hardcoded links to Explore and update them to the standard URL pattern.
    - Chore: Remove deprecated DataSourceAPI methods.
    - Data: Remove deprecated types and functions from valueMappings.
    - Elasticsearch: Remove browser access mode.
    - Elasticsearch: Remove support for versions after their end of the life (&lt;7.10.0).
    - Explore: Remove support for legacy, compact format URLs.
    - Graph: Deprecate Graph (old) and make it no longer a visualization option for new panels.
    - `setExploreQueryField`, `setExploreMetricsQueryField` and `setExploreLogsQueryField` are now deprecated and will
      be removed in a future release. If you need to set a different query editor for Explore, conditionally render
      based on `props.app` in your regular query editor.
  * Changes:
    - User: Fix externalUserId not being populated.
      If you used any of these components please use them from grafana/experimental from now on:
       - AccessoryButton
       - EditorFieldGroup
       - EditorHeader
       - EditorField
       - EditorRow
       - EditorList
       - EditorRows
       - EditorSwitch
       - FlexItem
       - Stack
       - InlineSelect
       - InputGroup
       - Space
    - Starting with 9.1.0, existing heatmap panels will start using a new implementation. This can be disabled by
      setting the `useLegacyHeatmapPanel` feature flag to true. It can be tested on a single dashbobard by adding
      `?__feature.useLegacyHeatmapPanel=true` to any dashboard URL.
    - Logger: Enable new logging format by default.
    - Loki: Enable new visual query builder by default.
    - Plugins: Remove plugin list panel.
    - Install wrapper scripts under /usr/sbin
    - Install actual binaries under /usr/libexec/grafana (or /usr/lib under older distributions) and create a simlink 
      for wrapper scripts and the service (which expect the binary to be under /usr/share/grafana/bin)
    - Chore: Upgrade typescript to 4.6.4.

mgr-daemon:

- Version 4.3.7-1
  * Update translation strings

spacecmd:

- Version 4.3.21-1
  * fix argument parsing of distribution_update (bsc#1210458)
- Version 4.3.20-1
  * Display activation key details after executing the corresponding command (bsc#1208719)
  * Show targetted packages before actually removing them (bsc#1207830)

uyuni-common-libs:

- Version 4.3.8-1
  * Allow default component for context manager

zypp-plugin-spacewalk:

- 1.0.14
  * SPEC cleanup
</description>
  <issue tracker="ijsc" id="MSQA-666"/>
  <issue tracker="bnc" id="1203599">some go packages fail to build after go1.18 -&gt; 1.19 transition</issue>
  <issue tracker="bnc" id="1207830">spacecmd: package_removeorphans and package_remove asks to remove packages without printing the packages before</issue>
  <issue tracker="bnc" id="1208719">spacecmd activationkey_details not showing any output</issue>
  <issue tracker="bnc" id="1210458">Changing autoinstallation distribution from command line</issue>
  <issue tracker="bnc" id="1210640">dracut network-legacy creates lease info file without IP version suffix</issue>
  <issue tracker="bnc" id="1210907">VUL-0: CVE-2023-1387: grafana: JWT URL-login flow leaks token to data sources through request parameter in proxy requests</issue>
  <issue tracker="bnc" id="1203185">VUL-0: CVE-2022-27664: go1.18,go1.19: net/http: handle server errors after sending GOAWAY</issue>
  <issue tracker="bnc" id="1203597">VUL-0: CVE-2022-35957: grafana: Escalation from admin to server admin when auth proxy is used</issue>
  <issue tracker="bnc" id="1203596">VUL-0: CVE-2022-36062: grafana: RBAC folders/dashboards privilege escalation</issue>
  <issue tracker="bnc" id="1192154">VUL-0: CVE-2021-3807: nodejs12,nodejs4,nodejs6,nodejs8,nodejs10,nodejs14: node-ansi-regex: Regular expression denial of service (ReDoS) matching ANSI escape codes</issue>
  <issue tracker="bnc" id="1192696">VUL-0: CVE-2021-3918: nodejs14, nodejs10, nodejs12, nodejs8: json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')</issue>
  <issue tracker="bnc" id="1200480">VUL-0: CVE-2021-43138: spacewalk-web: a malicious user can obtain privileges via the mapValues() method</issue>
  <issue tracker="bnc" id="1201539">VUL-0: CVE-2022-31107: grafana: OAuth account takeover</issue>
  <issue tracker="bnc" id="1201535">VUL-0: CVE-2022-31097: grafana: stored XSS vulnerability</issue>
  <issue tracker="bnc" id="1209645">VUL-0: CVE-2023-1410: grafana: Stored XSS in Graphite FunctionDescription tooltip</issue>
  <issue tracker="bnc" id="1204501">VUL-0: CVE-2022-32149: grafana,cni,rekor,go1.19,terraform,go1.18,cri-o: golang: golang.org/x/text/language: ParseAcceptLanguage takes a long time to parse complex tags</issue>
  <issue tracker="jsc" id="PED-3694"/>
  <issue tracker="jsc" id="PED-3576"/>
  <issue tracker="jsc" id="PED-3694"/>
  <issue tracker="cve" id="2022-46146"/>
  <issue tracker="cve" id="2022-41715"/>
  <issue tracker="cve" id="2023-1387"/>
  <issue tracker="cve" id="2023-1410"/>
  <issue tracker="cve" id="2022-32149"/>
  <issue tracker="cve" id="2022-27664"/>
  <issue tracker="cve" id="2022-35957"/>
  <issue tracker="cve" id="2022-36062"/>
  <issue tracker="cve" id="2020-7753"/>
  <issue tracker="cve" id="2021-3807"/>
  <issue tracker="cve" id="2021-3918"/>
  <issue tracker="cve" id="2021-43138"/>
  <issue tracker="cve" id="2022-0155"/>
  <issue tracker="cve" id="2022-31107"/>
  <issue tracker="cve" id="2022-31097"/>
</patchinfo>

Places

File _patchinfo of Package patchinfo.28934

Places