In Async before 2.6.4 and 3.x before 3.2.2, a malicious user can obtain privileges via the mapValues() method, aka lib/internal/iterator.js createObjectIterator prototype pollution.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In Async before 2.6.4 and 3.x before 3.2.2, a malicious user can obtain privileges via the mapValues()     method, aka lib/internal/iterator.js createObjectIterator prototype pollution. (CVE-2021-43138)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In Async before 2.6.4 and 3.x before 3.2.2, a malicious user can obtain privileges via the mapValues()
    method, aka lib/internal/iterator.js createObjectIterator prototype pollution. (CVE-2021-43138)

The remote Fedora 38 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2022-8ca9330e57 advisory.

    Automatic update for python-engineio-4.3.4-2.fc38.

    ##### **Changelog**

    ```
    * Thu Sep 15 2022 Benjamin A. Beasley <code@musicinmybrain.net> 4.3.4-2
    - Dont ship package-lock.json files with the examples
    - This keeps from having automated bugs filed for irrelevant CVEs in NPM       packages that are mentioned there. See RHBZ#2127005.

    ```

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of IBM Cognos Analytics installed on the remote host is prior to 11.1.7 FP8, 11.2.4 FP3, or 12.0.2. It is, therefore, affected by multiple vulnerabilities as referenced in the IBM Security Bulletin No. 7123154, including the following:

  - When deserializing untrusted or corrupted data, it is possible for a reader to consume memory beyond the   allowed constraints and thus lead to out of memory on the system. This issue affects Java applications using   Apache Avro Java SDK up to and including 1.11.2. Users should update to apache-avro version 1.11.3 which   addresses this issue. (CVE-2023-39410)

  - In order to decrypt SM2 encrypted data an application is expected to call the API function   EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the   'out' parameter can be NULL and, on exit, the 'outlen' parameter is populated with the buffer size required   to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call   EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the 'out' parameter. A bug in the   implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the   plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by   the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a   second time with a buffer that is too small. A malicious attacker who is able present SM2 content for   decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of   62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour   or causing the application to crash. The location of the buffer is application dependent but is typically   heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). (CVE-2021-3711)

  - SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization.
  Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using   SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend   upgrading to version 2.0 and beyond. (CVE-2022-1471)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:0487-1 advisory.

    golang-github-lusitaniae-apache_exporter:

    - Do not strip if SUSE Linux Enterprise 15 SP3
    - Exclude debug for Red Hat Enterprise Linux >= 8
    - Build with Go >= 1.20 when the OS is not Red Hat Enterprise Linux

    mgr-daemon:

    - Version 4.3.8-1
      * Update translation strings

    prometheus-postgres_exporter:

    - Remove duplicated call to systemd requirements
    - Do not build debug if Red Hat Enterprise Linux >= 8
    - Do not strip if SUSE Linux Enterprise 15 SP3
    - Build at least with with Go >= 1.18 on Red Hat Enterprise Linux
    - Build with Go >= 1.20 elsewhere

    spacecmd:

    - Version 4.3.26-1
      * Update translation strings

    spacewalk-client-tools:

    - Version 4.3.18-1
      * Update translation strings

    uyuni-proxy-systemd-services:

    - Version 4.3.10-1
      * Update the image version
    - Version 4.3.9-1
      * Integrate the containerized proxy into the usual rel-eng workflow

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:3761-1 advisory.

    Release notes for SUSE Manager:

    - Update to SUSE Manager 4.3.2
      * Containerized proxy and RBS are now fully supported
      * HTTP API is now fully supported
      * Ubuntu 22.04 is now supported as a client
      * Cobbler has been upgraded to version 3.3.3 which also includes building ISOs with UEFI support
      * pip support has been added for the Salt Bundle
      * Prometheus exporter for Apache has been upgraded to 0.10.0
      * CVEs fixed: CVE-2021-41411, CVE-2021-42740, CVE-2021-43138, CVE-2022-0860, CVE-2022-31129
      * Bugs mentioned:
        bsc#1191857, bsc#1195624, bsc#1196729, bsc#1197027, bsc#1198168         bsc#1198903, bsc#1199726, bsc#1200480, bsc#1200573, bsc#1200629         bsc#1201210, bsc#1201220, bsc#1201260, bsc#1201626, bsc#1201753         bsc#1201788, bsc#1201913, bsc#1201918, bsc#1202271, bsc#1202272         bsc#1202367, bsc#1202455, bsc#1202464, bsc#1202602, bsc#1202728         bsc#1202729, bsc#1202805, bsc#1202899, bsc#1203026, bsc#1203049         bsc#1203056, bsc#1203169, bsc#1203287, bsc#1203288, bsc#1203385         bsc#1203406, bsc#1203422, bsc#1203449, bsc#1203478, bsc#1203484         bsc#1203564, bsc#1203585, bsc#1203611

    Release notes for SUSE Manager Proxy:

    - Update to SUSE Manager 4.3.2
      * Containerized proxy and RBS are now fully supported
      * CVEs fixed: CVE-2021-42740, CVE-2021-43138, CVE-2022-31129
      * Bugs mentioned:
        bsc#1198168, bsc#1198903, bsc#1200480, bsc#1201589, bsc#1201788         bsc#1203287, bsc#1203288, bsc#1203585

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:3750-1 advisory.

    cobbler:

    - Consider case of 'next_server' being a hostname during migration of Cobbler collections.
    - Fix problem with 'proxy_url_ext' setting being None type.
    - Fix settings migration schema to work while upgrading on existing running       Uyuni and SUSE Manager servers running with old Cobbler settings (bsc#1203478)
    - Do generate boot menus even if no profiles or systems - only local boot
    - Avoid crashing running buildiso in certain conditions.
    - Fix issue that a custom kernel with the extension '.kernel' is not       accepted by 'cobbler distro add'
    - Fix issue with 'get_item_resolved_value' that prevented it from       returning in cases where a complex object would have been returned
    - Fix issue where the logs would have been spammed with 'grab_tree'       messages that are meant for debugging
    - Buildiso - Fix DNS append line generation
    - Change apache2 conf dir for SUSE distros to allow integration with       Uyuni and SUSE Manager
    - Avoid permissions errors during cobbler sync
    - Update to version 3.3.3
    - Add UEFI capabilities to 'cobbler buildiso' (jsc#SUMA-112)
    - Relevant changes on this release:
      * New:
        * Uyuni Proxies can now be set with the schema validation.
        * Cobbler should now build on AlmaLinux.
        * The initrd is not required anymore as it is an optional file.
        * XML-RPC: Added dump_vars endpoint. This is intended to replace get_blended_data as of 3.4.0.
        * XML-RPC: Added get_item_resolved_value & set_item_resolved_value endpoints.
      * Breaking Changes:
        * The field virt_file_size is now a float and the related settings as well.
      * Changes:
        * The error messages for duplicated objects now contains the name of the duplicated object.
      * Bugfixes:
        * Dictionaries had the wrong value set for <<inherit>>.
        * There were some cases in which the autoinstallation manager was handed the wrong object and then     crashed.
        * The inheritance of the owners field was fixed.
        * Serial Console options should not contain bogous -1 value anymore.
        * HTTP API should not throw permission errors anymore.
        * During build the log was not visible due to a custom logger without output.
        * cobbler mkloaders now also copies dependencies of menu.c32.
        * We now generate the grub configuration for the architectures correct again.
        * virt_file_size now is a float at all times.
        * Cobbler should restart successfully now if you have attached an image to a system.
        * If you have a system named default the bootloader was not removed properly before.
        * cobbler buildiso: The isolinux.cfg was not properly formatted.
        * There were unharmful templating errors in the log related to redhat_management_type. The parts     depending on this           were removed.
        * The DNS managers were non-functional before because of a not existing function call.
        * cobbler buildiso failed with --tmpdirs that don't end in buildiso.
        * cobbler buildiso had outdated docs and help messages for some parameters.
        * cobbler import: It was impossible to import Rocky Linux 8.5 successfully.
        * Cobbler created duplicated settings files before.
        * cobbler sync was broken by refactoring to shell=False before.
    - CVE-2022-0860: Improper Authorization in Cobbler. (bsc#1197027)
    - Version 3.3.0 fixed jsc#SUMA-112
    - Update to version 3.3.2
        * cobbler sync doesn't have to be executed no more after enable_ipxe was flipped
        * Auth: Support for Global Secure Catalog via LDAP provider
        * Reposync now deletes old metadata to prevent metadata merge conflicts
        * The automigration of the settings is now not enabled per default.
        * We removed ppc from RedHat EL 7 as it is not supported
        * Network interface is not subscriptable errors were fixed
        * The stacktraces related to the package and file pre & post triggers should no longer appear
        * You should be able to add multiple initrds if needed again
        * Debian: Fix regex for SHIM_FILE which now provides a working reasonable default

    drools:

    - CVE-2021-41411: XML External Entity injection in KieModuleModelImpl.java (bsc#1200629)

    image-sync-formula:

    - Update to version 0.1.1661440542.6cbe0da
      * Sort boot images by version instead of name-version (bsc#1196729)
      * Do not send events if syncing fails

    inter-server-sync:

      * Compress exported sql data and decompress during import
      * Add gzip dependency to decompress data file during import process

    locale-formula:

    - Update to version 0.3
      * Remove .map.gz from kb_map dictionary (bsc#1203406)

    python-urlgrabber:

    - Avoid crashing when setting URLGRABBER_DEBUG=1 environment variable

    reprepro:

    - Update from version 5.3.0 to version 5.4.0
      * Add shunit2 based tests
      * Support multiple versions
      * Add the commands move, movesrc, movematched, movefilter
      * Add Limit and Archive option
      * fix manpage to add the behaviour if reprepro is linked against liblzma
      * Mark 'dumpcontents' command as deprecated

    saltboot-formula:

    - Update to version 0.1.1661440542.6cbe0da
      * Fallback to local boot if the configured image is not synced
      * Support salt bundle

    spacecmd:

    - Version 4.3.15-1
      * Process date values in spacecmd api calls (bsc#1198903)

    spacewalk-admin:

    - Version 4.3.10-1
      * Ensure 'cobbler mkloaders' is executed after restarting services
      * Add --help option to mgr-monitoring-ctl
      * reportdb access: force new report_db_sslrootcert if previous default is set

    spacewalk-backend:

    - Version 4.3.16-1
      * Prevent mixing credentials for proxy and repository server         while using basic authentication and avoid hiding errors         i.e. timeouts while having proxy settings issues         with extra logging in verbose mode (bsc#1201788)
      * Fix the condition of hiding the token from URL on logging
      * export armored GPG key to salt filesystem as well
      * Upgrade Cobbler requirement to 3.3.3 or later
      * Make reposync use the configured http proxy with mirrorlist (bsc#1198168)

    spacewalk-certs-tools:

    - Version 4.3.15-1
      * fix mgr-ssl-cert-setup for root CAs which do not set authorityKeyIdentifier (bsc#1203585)

    spacewalk-client-tools:

    - Version 4.3.12-1
      * Update translation strings

    spacewalk-java:

    - version 4.3.38-1
      * delay hardware refresh action to avoid missing channels (bsc#1204208)
    - Version 4.3.37-1
      * Fix get_item_resolved_value call
    - Version 4.3.36-1
      * Fix prerequisite action serialization (bsc#1202899, bsc#1203484)
      * Fix hardware update where there is no DNS FQDN changes (bsc#1203611)
      * Fix UI crash when filtering on systems list (bsc#1203169)
      * Filter out successors that have no repositories on SP migration (bsc#1202367)
      * Reduced the usage of deprecated Hibernate API
      * Use mgrnet.dns_fqdns module to improve FQDN detection (bsc#1199726)
      * Support Pay-as-you-go new CA location for SUSE Linux Enterprise Server 15 SP4 and higher (bsc#1202729)
      * Fixed pagination for completed/failed systems in action details
      * Add support in rhn.conf for smtp port, auth, ssl/tls config
      * Calculate dependencies between cloned channels of vendor channels (bsc#1201626)
      * Fix sync for external repositories (bsc#1201753)
      * Detect the clients running on Amazon EC2 (bsc#1195624)
      * Adjust cobbler requirement to version 3.3.3
      * Support inherited values for kernel options from Cobbler API
      * Fix virtFileSize type after cobbler upgrade
      * Redefine available power_management.types for cobbler >= 3.3.1
      * fix state.apply result parsing in test mode (bsc#1201913)
      * require tomcat native interface to prevent misleading warning         in tomcat startup log (bsc#1202455)
      * Reduce the length of image channel URL (bsc#1201220)
      * Fixed formula deselection in systemgroup (bsc#1202271)
      * Added a new configuration property to allow custom channels to         be synced together with vendor channels.
      * add onlyRelevant argument to addErrataUpdate API
      * fix taskomatic task remain in progress

    spacewalk-search:

    - Version 4.3.7-1
      * update dependencies after package rename

    spacewalk-setup:

    - version 4.3.12
      * Fix detected issues to perform migration of Cobbler settings         and collections.

    - Version 4.3.11-1
      * Trigger migration of Cobbler settings and collections if necessary         during package installation (bsc#1203478)
      * Execute 'cobbler mkloaders' when setting up cobbler
      * Adjust next_server cobbler settings for cobbler >= 3.3.1
      * fix prototype missmatch in idn_to_ascii (bsc#1203385)

    spacewalk-utils:

    - Version 4.3.14-1
      * Make spacewalk-hostname-rename working with settings.yaml cobbler config file (bsc#1203564)
      * spacewalk-common-channels now syncs the channels automatically         on creation, if the new configuration property named         'unify_custom_channel_management' is enabled

    spacewalk-web:

    - Version 4.3.24-1
      * Upgrade moment-timezone
      * CVE-2021-43138: Obtain privileges via the `mapValues()` method. (bsc#1200480)
      * CVE-2021-42740: Command injection in the shell-quote package. (bsc#1203287)
      * CVE-2022-31129: Denial-of-Service moment: inefficient parsing algorithm (bsc#1203288)
      * Fix table header layout for unselectable tables

    subscription-matcher:

    - Added Guava maximum version requirement

    susemanager:

    - Version 4.3.19-1
      * mark new dependencies for python-py optional in bootstrap repo         to fix generation for older service packs (bsc#1203449)
      * add bootstrap repository definition for OES2023 (bsc#1202602)
      * add missing packages on SUSE Linux Enterprise Server 15
      * remove server-migrator.sh from SUSE Manager installations (bsc#1202728)
      * create bootstrap repository data for Ubuntu 22.04 Vendor Channels
      * remove obsoleted sysv init script (bsc#1191857)
      * mgr-create-bootstrap-repo: flush directory also when called         for a specific label (bsc#1200573)
      * pg-migrate-x-to-y.sh: improve output (bsc#1201260)
      * remove python-tornado from bootstrap repo, since no longer         required for salt version >= 3000
      * add missing packages on SUSE Linux Enterprise Server 12 SP5 bootstrap repo (bsc#1201918)
      * revert 'bootstrap repo: set optional packages'

    susemanager-build-keys:

    - Add release and auxiliary GPG keys for RedHat
    - Add keys for Rocky Linux 9
      * RPM-GPG-KEY-redhat-release
      * RPM-GPG-KEY-redhat-auxiliary
      * RPM-GPG-KEY-Rocky-9

    susemanager-docs_en:

    - Removed Debian 9 references due to end of life and added missing Debian 11 info
    - Fixed description of default notification settings (bsc#1203422)
    - Added missing Debian 11 references
    - Documented helm deployment of the proxy on k3s and MetalLB in       Installation and Upgrade Guide
    - Added secure mail communication settings in Administration Guide
    - Fixed path to state and pillar files
    - Documented how pxeboot works with Secure Boot enabled in Client       Configuration Guide
    - Add repository via proxy issues troubleshooting page
    - Change import GPG key description
    - Added SLE Micro 5.2 and 5.3 as available as a technology preview       in Client Configuration Guide, and the IBM Z architecture for 5.1,       5.2, and 5.3
    - Added command to remove the obsolete Python module on SUSE Manager       Server 4.1 in the Installation and Upgrade Guide (bsc#1203026)
    - Mention CA certificate directory in the proxy setup description in the       Installation and Upgrade Guide (bsc#1202805)
    - Documented mandatory channels in the Disconnected Setup chapter of the       Administration Guide (bsc#1202464)
    - Documented how to onboard Ubuntu clients with the Salt bundle as a       regular user
    - Documented how to onboard Debian clients with the Salt bundle or       plain Salt as a regular user
    - Fixed the names of updates channels for Leap
    - Fixed errors in OpenSCAP chapter of Administration Guide
    - Removed CentOS 8 from the list of supported client systems
    - Extend the notes about using noexec option for /tmp and /var/tmp       (bsc#1201210)
    - Added Extend Salt Bundle functionality with Python packages using pip
    - Salt Configuration Modules are no longer Technology Preview in       the Salt Guide

    susemanager-schema:

    - Version 4.3.14-1
      * Add subtypes for Amazon EC2 virtual instances (bsc#1195624)
      * Fix migration of image actions (bsc#1202272)
      * improve schema compatibility with Amazon RDS

    susemanager-sls:

    - Version 4.3.25-1
      * Fix mgrnet availability check
      * Remove dependence on Kiwi libraries
      * disable always the bootstrap repository also when         'mgr_disable_local_repos' is set to False
      * Use mgrnet.dns_fqdns module to improve FQDN detection (bsc#1199726)
      * fix syntax error - remove trailing colon (bsc#1203049)
      * Add mgrnet salt module with mgrnet.dns_fqnd function implementation         allowing to get all possible FQDNs from DNS (bsc#1199726)
      * Copy grains file with util.mgr_switch_to_venv_minion state apply (bsc#1203056)
      * Remove the message 'rpm: command not found' on using Salt SSH         with Debian based systems which has no Salt Bundle

    susemanager-sync-data:

    - Version 4.3.9-1
      * add oes2023 (bsc#1202602)
      * add Ubuntu 22.04 amd64

    susemanager-tftpsync:

    - Version 4.3.2-1
      * Adjust sync_post_tftpd_proxies module to cobbler >= 3.3.1

    uyuni-common-libs:

    - Version 4.3.6-1
      * Do not allow creating path if nonexistent user or group in fileutils.

    uyuni-reportdb-schema:

    - Version 4.3.6-1
      * improve schema compatibility with Amazon RDS

    How to apply this update:

    1. Log in as root user to the SUSE Manager server.
    2. Stop the Spacewalk service:
    `spacewalk-service stop`     3. Apply the patch using either zypper patch or YaST Online Update.
    4. Start the Spacewalk service:
    `spacewalk-service start`

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2023:2575-1 advisory.

    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 < 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 `<form>` the           default value was `submit` per the specification. You can preserve the old behavior by explicitly     setting the           type attribute: `<Button type='submit' />`
        - The `Rename by regex` transformation has been improved to allow global patterns of the form           `/<stringToReplace>/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 `/(.*)/`
        - `<Select />` 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 `&left=['now-1h','now'...]`. The standard explore URLs follow a     key/value           pattern, for example `&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 (<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.

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2023:2578-1 advisory.

    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 < 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 `<form>` the           default value was `submit` per the specification. You can preserve the old behavior by explicitly     setting the           type attribute: `<Button type='submit' />`
        - The `Rename by regex` transformation has been improved to allow global patterns of the form           `/<stringToReplace>/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 `/(.*)/`
        - `<Select />` 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 `&left=['now-1h','now'...]`. The standard explore URLs follow a     key/value           pattern, for example `&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 (<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

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 37 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2023-ce8943223c advisory.

    Add patches for CVE-2021-43138, CVE-2022-3517, CVE-2020-7677

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 36 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2023-18fd476362 advisory.

    Add patches for CVE-2021-43138, CVE-2022-3517, CVE-2020-7677

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of IBM Cognos Analytics installed on the remote host is affected by multiple vulnerabilities, including the following:

  - OpenSSL is vulnerable to a buffer overflow, caused by improper bounds checking by the EVP_PKEY_decrypt()     function within implementation of the SM2 decryption. By sending specially crafted SM2 content, a remote     attacker could overflow a buffer and execute arbitrary code on the system or cause the application to     crash. (CVE-2021-3711)

  - Async could allow a remote attacker to execute arbitrary code on the system, caused by prototype pollution     in the mapValues() method. By persuading a victim to open a specially-crafted file, an attacker could     exploit this vulnerability to execute arbitrary code on the system.
    (CVE-2021-43138)

  - Apache Commons IO could allow a remote attacker to traverse directories on the system, caused by improper     input validation by the FileNameUtils.normalize method. An attacker could send a specially-crafted URL     request containing 'dot dot' sequences (/../) to view arbitrary files on the system.
    (CVE-2021-29425)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
224150	Linux Distros Unpatched Vulnerability : CVE-2021-43138	Nessus	Misc.	Local	high
414741	SCA: security update for async (GHSA-fwr7-v2mv-hh25)	Tenable Cloud Security	SCA Checks	Local	high
414741	SCA: security update for async (GHSA-fwr7-v2mv-hh25)	Tenable Self-Hosted Container Security	SCA Checks	Local	high
211097	Fedora 38 : python-engineio (2022-8ca9330e57)	Nessus	Fedora Local Security Checks	Local	high
193868	IBM Cognos Analytics 11.1.1 < 11.1.7 FP8 / 11.2.x < 11.2.4 FP3 / 12.0.x < 12.0.2 (7123154)	Nessus	CGI abuses	Remote	critical
190632	SUSE SLES15: golang-github-lusitaniae-apache_exporter / etc (SUSE-SU-2024:0487-1)	Nessus	SuSE Local Security Checks	Local	critical
181674	SUSE SLES15 Security Update : release-notes-susemanager, release-notes-susemanager-proxy (SUSE-SU-2022:3761-1)	Nessus	SuSE Local Security Checks	Local	high
181673	SUSE SLES15: cobbler / drools / image-sync-formula / inter-server-sync / etc (SUSE-SU-2022:3750-1)	Nessus	SuSE Local Security Checks	Local	high
177500	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : SUSE Manager Client Tools (SUSE-SU-2023:2575-1)	Nessus	SuSE Local Security Checks	Local	high
177497	SUSE SLES15: bind / bind-chrootenv / bind-devel / bind-devel-32bit / bind-doc / etc (SUSE-SU-2023:2578-1)	Nessus	SuSE Local Security Checks	Local	high
170237	Fedora 37 : yarnpkg (2023-ce8943223c)	Nessus	Fedora Local Security Checks	Local	critical
170235	Fedora 36 : yarnpkg (2023-18fd476362)	Nessus	Fedora Local Security Checks	Local	critical
166606	IBM Cognos Analytics Multiple Vulnerabilities (6828527)	Nessus	CGI abuses	Remote	critical

Detections

Analytics

CVE-2021-43138

high

Tenable Plugins

high

high

high

high

critical

critical

high

high

high

high

critical

critical

critical