The remote Oracle Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2022-0350 advisory.

    nodejs     [1:14.18.2-2]
    - Add missing fixes
    - Resolves: RHBZ#2027642, RHBZ#2027635

    [1:14.18.2-1]
    - Resolves: RHBZ#2027609
    - Resolves: RHBZ#2027649, RHBZ#2027646, RHBZ#2027642, RHBZ#2027635
    - Rebase to new version to fix CVEs

Tenable has extracted the preceding description block directly from the Oracle Linux 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 SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:0531-1 advisory.

  - All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via     splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time     complexity. (CVE-2021-23343)

  - The npm package tar (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File     Creation/Overwrite vulnerability via insufficient symlink protection. `node-tar` aims to guarantee that     any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved     by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary     `stat` calls to determine whether a given path is a directory, paths are cached when directories are     created. This logic was insufficient when extracting tar files that contained both a directory and a     symlink with the same name as the directory. This order of operations resulted in the directory being     created and added to the `node-tar` directory cache. When a directory is present in the directory cache,     subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks     for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it     was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted     tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that     location, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.3,     4.4.15, 5.0.7 and 6.1.2. (CVE-2021-32803)

  - The npm package tar (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File     Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent     extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths`     flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file     paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This     logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`.
    `node-tar` would only strip a single path root from such paths. When given an absolute file path with     repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute     path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2,     4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom     `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute     paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in     later versions of tar. (CVE-2021-32804)

  - ansi-regex is vulnerable to Inefficient Regular Expression Complexity (CVE-2021-3807)

  - json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype     Pollution') (CVE-2021-3918)

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 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:0563-1 advisory.

    - CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
    - CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and     overwrite (bsc#1191963).
    - CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file     creation and overwrite (bsc#1191962).
    - CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema     (bsc#1192696).
    - CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-     ansi-regex (bsc#1192154).

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 SUSE15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2022:0715-1 advisory.

  - All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via     splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time     complexity. (CVE-2021-23343)

  - The npm package tar (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File     Creation/Overwrite vulnerability via insufficient symlink protection. `node-tar` aims to guarantee that     any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved     by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary     `stat` calls to determine whether a given path is a directory, paths are cached when directories are     created. This logic was insufficient when extracting tar files that contained both a directory and a     symlink with the same name as the directory. This order of operations resulted in the directory being     created and added to the `node-tar` directory cache. When a directory is present in the directory cache,     subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks     for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it     was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted     tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that     location, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.3,     4.4.15, 5.0.7 and 6.1.2. (CVE-2021-32803)

  - The npm package tar (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File     Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent     extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths`     flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file     paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This     logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`.
    `node-tar` would only strip a single path root from such paths. When given an absolute file path with     repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute     path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2,     4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom     `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute     paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in     later versions of tar. (CVE-2021-32804)

  - ansi-regex is vulnerable to Inefficient Regular Expression Complexity (CVE-2021-3807)

  - json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype     Pollution') (CVE-2021-3918)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
157333	Oracle Linux 8 : nodejs:14 (ELSA-2022-0350)	Nessus	Oracle Linux Local Security Checks	2022/2/2	2024/11/1	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
158221	SUSE SLES12 Security Update : nodejs12 (SUSE-SU-2022:0531-1)	Nessus	SuSE Local Security Checks	2022/2/22	2023/7/13	critical
158357	SUSE SLES15 Security Update : nodejs8 (SUSE-SU-2022:0563-1)	Nessus	SuSE Local Security Checks	2022/2/24	2026/6/26	critical
158624	openSUSE 15 Security Update : nodejs14 (openSUSE-SU-2022:0715-1)	Nessus	SuSE Local Security Checks	2022/3/5	2023/11/6	critical

检测

插件搜索

critical

high

critical

critical

critical