The version of application-gateway-kubernetes-ingress / cf-cli / cni / containerized-data-importer / containernetworking-plugins / gh / keda / kubevirt installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2022-32149 advisory.

  - An attacker May cause a denial of service by crafting an Accept-Language header which ParseAcceptLanguage     will take significant time to parse. (CVE-2022-32149)

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 application-gateway-kubernetes-ingress / cf-cli / cni / containerized-data-importer / containernetworking-plugins / gh / keda / kubevirt installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2022-32149 advisory.

  - An attacker May cause a denial of service by crafting an Accept-Language header which ParseAcceptLanguage     will take significant time to parse. (CVE-2022-32149)

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 SLES12 / SLES_SAP12 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2023:3867-1 advisory.

    golang-github-lusitaniae-apache_exporter:

    - Security issues fixed:
      * CVE-2022-32149: Fix denial of service vulnerability (bsc#1204501)
      * CVE-2022-41723: Fix uncontrolled resource consumption (bsc#1208270)
      * CVE-2022-46146: Fix authentication bypass vulnarability (bsc#1208046)
    - Changes and bugs fixed:
      * Updated to 1.0.0 (jsc#PED-5405)
        - Improved flag parsing
        - Added support for custom headers
      * Changes from 0.13.1
        - Fix panic caused by missing flagConfig options
      * Added AppArmor profile
      * Added sandboxing options to systemd service unit
      * Build using promu
      * Build with Go 1.19
      * Exclude s390 architecture

    golang-github-prometheus-alertmanager:

    - CVE-2023-29409: Restrict RSA keys in certificates to less than or equal to 8192 bits to avoid DoSing     client/server       while validating signatures for extremely large RSA keys. (bsc#1213880)       There are no direct source changes. The CVE is fixed rebuilding the sources with the patched Go version.

    golang-github-prometheus-node_exporter:

    - CVE-2023-29409: Restrict RSA keys in certificates to less than or equal to 8192 bits to avoid DoSing     client/server       while validating signatures for extremely large RSA keys. (bsc#1213880)       There are no direct source changes. The CVE is fixed rebuilding the sources with the patched Go version.

    golang-github-prometheus-prometheus:

    - This update introduces breaking changes. Please, read carefully the provided informations.
    - Security issues fixed:
      * CVE-2022-41723: Fix uncontrolled resource consumption by updating Go to version 1.20.1 (bsc#1208298)
    - Updated to 2.45.0 (jsc#PED-5406):
      * [FEATURE] API: New limit parameter to limit the number of items returned by `/api/v1/status/tsdb`     endpoint
      * [FEATURE] Config: Add limits to global config
      * [FEATURE] Consul SD: Added support for `path_prefix`
      * [FEATURE] Native histograms: Add option to scrape both classic and native histograms.
      * [FEATURE] Native histograms: Added support for two more arithmetic operators `avg_over_time` and     `sum_over_time`
      * [FEATURE] Promtool: When providing the block id, only one block will be loaded and analyzed
      * [FEATURE] Remote-write: New Azure ad configuration to support remote writing directly to Azure Monitor     workspace
      * [FEATURE] TSDB: Samples per chunk are now configurable with flag `storage.tsdb.samples-per-chunk`. By     default set         to its former value 120
      * [ENHANCEMENT] Native histograms: bucket size can now be limited to avoid scrape fails
      * [ENHANCEMENT] TSDB: Dropped series are now deleted from the WAL sooner
      * [BUGFIX] Native histograms: ChunkSeries iterator now checks if a new sample can be appended to the     open chunk
      * [BUGFIX] Native histograms: Fix Histogram Appender `Appendable()` segfault
      * [BUGFIX] Native histograms: Fix setting reset header to gauge histograms in seriesToChunkEncoder
      * [BUGFIX] TSDB: Tombstone intervals are not modified after Get() call
      * [BUGFIX] TSDB: Use path/filepath to set the WAL directory.
    - Changes from 2.44.0:
      * [FEATURE] Remote-read: Handle native histograms
      * [FEATURE] Promtool: Health and readiness check of prometheus server in CLI
      * [FEATURE] PromQL: Add `query_samples_total` metric, the total number of samples loaded by all queries
      * [ENHANCEMENT] Storage: Optimise buffer used to iterate through samples
      * [ENHANCEMENT] Scrape: Reduce memory allocations on target labels
      * [ENHANCEMENT] PromQL: Use faster heap method for `topk()` / `bottomk()`
      * [ENHANCEMENT] Rules API: Allow filtering by rule name
      * [ENHANCEMENT] Native Histograms: Various fixes and improvements
      * [ENHANCEMENT] UI: Search of scraping pools is now case-insensitive
      * [ENHANCEMENT] TSDB: Add an affirmative log message for successful WAL repair
      * [BUGFIX] TSDB: Block compaction failed when shutting down
      * [BUGFIX] TSDB: Out-of-order chunks could be ignored if the write-behind log was deleted
    - Changes from 2.43.1
      * [BUGFIX] Labels: Set() after Del() would be ignored, which broke some relabeling rules
    - Changes from 2.43.0:
      * [FEATURE] Promtool: Add HTTP client configuration to query commands
      * [FEATURE] Scrape: Add `include_scrape_configs` to include scrape configs from different files
      * [FEATURE] HTTP client: Add `no_proxy` to exclude URLs from proxied requests
      * [FEATURE] HTTP client: Add `proxy_from_enviroment` to read proxies from env variables
      * [ENHANCEMENT] API: Add support for setting lookback delta per query via the API
      * [ENHANCEMENT] API: Change HTTP status code from 503/422 to 499 if a request is canceled
      * [ENHANCEMENT] Scrape: Allow exemplars for all metric types
      * [ENHANCEMENT] TSDB: Add metrics for head chunks and WAL folders size
      * [ENHANCEMENT] TSDB: Automatically remove incorrect snapshot with index that is ahead of WAL
      * [ENHANCEMENT] TSDB: Improve Prometheus parser error outputs to be more comprehensible
      * [ENHANCEMENT] UI: Scope `group by` labels to metric in autocompletion
      * [BUGFIX] Scrape: Fix `prometheus_target_scrape_pool_target_limit` metric not set before reloading
      * [BUGFIX] TSDB: Correctly update `prometheus_tsdb_head_chunks_removed_total` and     `prometheus_tsdb_head_chunks`         metrics when reading WAL
      * [BUGFIX] TSDB: Use the correct unit (seconds) when recording out-of-order append deltas in the         `prometheus_tsdb_sample_ooo_delta` metric
    - Changes from 2.42.0:
      This release comes with a new feature coverage for native histograms and breaking changes.
      If you are trying native histograms already, we recommend you remove the `wal` directory when upgrading.
    Because the       old WAL record for native histograms is not backward compatible in v2.42.0, this will lead to some data     loss for the       latest data. Additionally, if you scrape 'float histograms' or use recording rules on native histograms     in v2.42.0       (which writes float histograms), it is a one-way street since older versions do not support float     histograms.
      * [CHANGE] **breaking** TSDB: Changed WAL record format for the experimental native histograms
      * [FEATURE] Add 'keep_firing_for' field to alerting rules
      * [FEATURE] Promtool: Add support of selecting timeseries for TSDB dump
      * [ENHANCEMENT] Agent: Native histogram support.
      * [ENHANCEMENT] Rules: Support native histograms in recording rules
      * [ENHANCEMENT] SD: Add container ID as a meta label for pod targets for Kubernetes
      * [ENHANCEMENT] SD: Add VM size label to azure service discovery
      * [ENHANCEMENT] Support native histograms in federation
      * [ENHANCEMENT] TSDB: Add gauge histogram support
      * [ENHANCEMENT] TSDB/Scrape: Support FloatHistogram that represents buckets as float64 values
      * [ENHANCEMENT] UI: Show individual scrape pools on /targets page
    - Changes from 2.41.0:
      * [FEATURE] Relabeling: Add keepequal and dropequal relabel actions
      * [FEATURE] Add support for HTTP proxy headers
      * [ENHANCEMENT] Reload private certificates when changed on disk
      * [ENHANCEMENT] Add max_version to specify maximum TLS version in tls_config
      * [ENHANCEMENT] Add goos and goarch labels to prometheus_build_info
      * [ENHANCEMENT] SD: Add proxy support for EC2 and LightSail SDs
      * [ENHANCEMENT] SD: Add new metric prometheus_sd_file_watcher_errors_total
      * [ENHANCEMENT] Remote Read: Use a pool to speed up marshalling
      * [ENHANCEMENT] TSDB: Improve handling of tombstoned chunks in iterators
      * [ENHANCEMENT] TSDB: Optimize postings offset table reading
      * [BUGFIX] Scrape: Validate the metric name, label names, and label values after relabeling
      * [BUGFIX] Remote Write receiver and rule manager: Fix error handling
    - Changes from 2.40.7:
      * [BUGFIX] TSDB: Fix queries involving negative buckets of native histograms
    - Changes from 2.40.5:
      * [BUGFIX] TSDB: Fix queries involving native histograms due to improper reset of iterators
    - Changes from 2.40.3:
      * [BUGFIX] TSDB: Fix compaction after a deletion is called
    - Changes from 2.40.2:
      * [BUGFIX] UI: Fix black-on-black metric name color in dark mode
    - Changes from 2.40.1:
      * [BUGFIX] TSDB: Fix alignment for atomic int64 for 32 bit architecture
      * [BUGFIX] Scrape: Fix accept headers
    - Changes from 2.40.0:
      * [FEATURE] Add experimental support for native histograms.
        Enable with the flag --enable-feature=native-histograms.
      * [FEATURE] SD: Add service discovery for OVHcloud
      * [ENHANCEMENT] Kubernetes SD: Use protobuf encoding
      * [ENHANCEMENT] TSDB: Use golang.org/x/exp/slices for improved sorting speed
      * [ENHANCEMENT] Consul SD: Add enterprise admin partitions. Adds __meta_consul_partition label. Adds     partition         config in consul_sd_config
      * [BUGFIX] API: Fix API error codes for /api/v1/labels and /api/v1/series
    - Changes from 2.39.1:
      * [BUGFIX] Rules: Fix notifier relabel changing the labels on active alerts
    - Changes from 2.39.0:
      * [FEATURE] experimental TSDB: Add support for ingesting out-of-order samples. This is configured via         out_of_order_time_window field in the config file; check config file docs for more info
      * [ENHANCEMENT] API: /-/healthy and /-/ready API calls now also respond to a HEAD request on top of     existing         GET support.
      * [ENHANCEMENT] PuppetDB SD: Add __meta_puppetdb_query label.
      * [ENHANCEMENT] AWS EC2 SD: Add __meta_ec2_region label.
      * [ENHANCEMENT] AWS Lightsail SD: Add __meta_lightsail_region label.
      * [ENHANCEMENT] Scrape: Optimise relabeling by re-using memory.
      * [ENHANCEMENT] TSDB: Improve WAL replay timings.
      * [ENHANCEMENT] TSDB: Optimise memory by not storing unnecessary data in the memory.
      * [ENHANCEMENT] TSDB: Allow overlapping blocks by default.
        --storage.tsdb.allow-overlapping-blocks now has no effect.
      * [ENHANCEMENT] UI: Click to copy label-value pair from query result to clipboard.
      * [BUGFIX] TSDB: Turn off isolation for Head compaction to fix a memory leak.
      * [BUGFIX] TSDB: Fix 'invalid magic number 0' error on Prometheus startup.
      * [BUGFIX] PromQL: Properly close file descriptor when logging unfinished queries.
      * [BUGFIX] Agent: Fix validation of flag options and prevent WAL from growing more than desired.
    - Changes from 2.38.0:
      * [FEATURE]: Web: Add a /api/v1/format_query HTTP API endpoint that allows pretty-formatting PromQL     expressions.
      * [FEATURE]: UI: Add support for formatting PromQL expressions in the UI.
      * [FEATURE]: DNS SD: Support MX records for discovering targets.
      * [FEATURE]: Templates: Add toTime() template function that allows converting sample timestamps to         Go time.Time values
      * [ENHANCEMENT]: Kubernetes SD: Add
        __meta_kubernetes_service_port_number meta label indicating the service port number.
        __meta_kubernetes_pod_container_image meta label indicating the container image.
      * [ENHANCEMENT]: PromQL: When a query panics, also log the query itself alongside the panic message.
      * [ENHANCEMENT]: UI: Tweak colors in the dark theme to improve the contrast ratio.
      * [ENHANCEMENT]: Web: Speed up calls to /api/v1/rules by avoiding locks and using atomic types instead.
      * [ENHANCEMENT]: Scrape: Add a no-default-scrape-port feature flag, which omits or removes any default     HTTP (:80)         or HTTPS (:443) ports in the target's scrape address.
      * [BUGFIX]: TSDB: In the WAL watcher metrics, expose the         type='exemplar' label instead of type='unknown' for exemplar records.
      * [BUGFIX]: TSDB: Fix race condition around allocating series IDs during chunk snapshot loading.

    golang-github-QubitProducts-exporter_exporter:

    - CVE-2023-29409: Restrict RSA keys in certificates to less than or equal to 8192 bits to avoid DoSing     client/server       while validating signatures for extremely large RSA keys. (bsc#1213880)       There are no direct source changes. The CVE is fixed rebuilding the sources with the patched Go version.

    grafana:

    - CVE-2023-29409: Restrict RSA keys in certificates to less than or equal to 8192 bits to avoid DoSing     client/server       while validating signatures for extremely large RSA keys. (bsc#1213880)       There are no direct source changes. The CVE is fixed rebuilding the sources with the patched Go version.

    prometheus-blackbox_exporter:

    - CVE-2023-29409: Restrict RSA keys in certificates to less than or equal to 8192 bits to avoid DoSing     client/server       while validating signatures for extremely large RSA keys. (bsc#1213880)       There are no direct source changes. The CVE is fixed rebuilding the sources with the patched Go version.

    prometheus-postgres_exporter:

    - CVE-2023-29409: Restrict RSA keys in certificates to less than or equal to 8192 bits to avoid DoSing     client/server       while validating signatures for extremely large RSA keys. (bsc#1213880)       There are no direct source changes. The CVE is fixed rebuilding the sources with the patched Go version.

    spacecmd:

    - Updated to 4.3.23-1
      * Update translation strings

    supportutils-plugin-susemanager-client:

    - Updated to 4.3.3-1
      * Write configured crypto-policy in supportconfig
      * Add cloud and Pay-as-you-go checks

    uyuni-common-libs:

    - Updated to 4.3.9-1
      * Workaround for python3-debian bug about collecting control file (bsc#1211525, bsc#1208692)

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 host is affected by the vulnerability described in GLSA-202210-14 (Gitea: Multiple Vulnerabilities)

  - Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9. (CVE-2022-1928)

  - An attacker may cause a denial of service by crafting an Accept-Language header which ParseAcceptLanguage     will take significant time to parse. (CVE-2022-32149)

  - In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper     access controls, an attacker could assign any issue to any project in Gitea (there was no permission check     for fetching the issue). As a result, the attacker would get access to private issue titles.
    (CVE-2022-38183)

  - Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are     mishandled. (CVE-2022-42968)

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 version of Splunk installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the SVD-2023-0808 advisory.

  - The go command may execute arbitrary code at build time when using cgo. This may occur when running go     get on a malicious module, or when running any other command which builds untrusted code. This is can by     triggered by linker flags, specified via a #cgo LDFLAGS directive. Flags containing embedded spaces are     mishandled, allowing disallowed flags to be smuggled through the LDFLAGS sanitization by including them in     the argument of another flag. This only affects usage of the gccgo compiler. (CVE-2023-29405)

  - When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by     finalizing the operation with a rename from a temporary name to the final target file name.In that rename     operation, it might accidentally *widen* the permissions for the target file, leaving the updated file     accessible to more users than intended. (CVE-2022-32207)

  - decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS. (CVE-2022-38900)

  - The got package before 12.1.0 (also fixed in 11.8.5) for Node.js allows a redirect to a UNIX socket.
    (CVE-2022-33987)

  - Prototype pollution vulnerability in function parseQuery in parseQuery.js in webpack loader-utils via the     name variable in parseQuery.js. This affects all versions prior to 1.4.1 and 2.0.3. (CVE-2022-37601)

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

ID	名前	製品	ファミリー	公開日	更新日	深刻度
215247	Azure Linux 3.0 Security Update: application-gateway-kubernetes-ingress / cf-cli / cni / containerized-data-importer / containernetworking-plugins / gh / keda / kubevirt (CVE-2022-32149)	Nessus	Azure Linux Local Security Checks	2025/2/10	2025/9/15	high
185997	CBL Mariner 2.0 Security Update: application-gateway-kubernetes-ingress / cf-cli / cni / containerized-data-importer / containernetworking-plugins / gh / keda / kubevirt (CVE-2022-32149)	Nessus	MarinerOS Local Security Checks	2023/11/19	2025/5/23	high
182172	SUSE SLES12 Security Update : SUSE Manager Client Tools (SUSE-SU-2023:3867-1)	Nessus	SuSE Local Security Checks	2023/9/29	2026/6/26	high
166729	GLSA-202210-14 : Gitea: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	2022/10/31	2023/10/6	critical
177500	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : SUSE Manager Client Tools (SUSE-SU-2023:2575-1)	Nessus	SuSE Local Security Checks	2023/6/22	2026/6/25	high
194928	Splunk Enterprise 8.2.0 < 8.2.12, 9.0.0 < 9.0.6, 9.1.0 < 9.1.1 (SVD-2023-0808)	Nessus	CGI abuses	2024/5/2	2024/7/29	critical

検出

プラグインの検索

high

high

high

critical

high

critical