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.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:1717-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)

  - Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
    (CVE-2021-44906)

  - node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor (CVE-2022-0235)

  - Due to the formatting logic of the console.table() function it was not safe to allow user controlled     input to be passed to the properties parameter while simultaneously passing a plain object with at least     one property as the first parameter, which could be __proto__. The prototype pollution has very limited     control, in that it only allows an empty string to be assigned to numerical keys of the object     prototype.Node.js >= 12.22.9, >= 14.18.3, >= 16.13.2, and >= 17.3.1 use a null protoype for the object     these properties are being assigned to. (CVE-2022-21824)

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:0704-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.

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.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:0704-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: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 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:0657-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.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:0657-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 SLES12 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:0569-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 SLES12 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:0570-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)

  - Due to the formatting logic of the console.table() function it was not safe to allow user controlled     input to be passed to the properties parameter while simultaneously passing a plain object with at least     one property as the first parameter, which could be __proto__. The prototype pollution has very limited     control, in that it only allows an empty string to be assigned to numerical keys of the object     prototype.Node.js >= 12.22.9, >= 14.18.3, >= 16.13.2, and >= 17.3.1 use a null protoype for the object     these properties are being assigned to. (CVE-2022-21824)

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.

  - 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 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 Rocky Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2021:3666 advisory.

  - Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application     crashes due to missing input validation of host names returned by Domain Name Servers in Node.js dns     library which can lead to output of wrong hostnames (leading to Domain Hijacking) and injection     vulnerabilities in applications using the library. (CVE-2021-22931)

  - 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)

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

The remote Rocky Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2021:3623 advisory.

  - Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application     crashes due to missing input validation of host names returned by Domain Name Servers in Node.js dns     library which can lead to output of wrong hostnames (leading to Domain Hijacking) and injection     vulnerabilities in applications using the library. (CVE-2021-22931)

  - 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)

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

Node.js reports : npm 6 update - node-tar, arborist, npm cli modules These are vulnerabilities in the node-tar, arborist, and npm cli modules which are related to the initial reports and subsequent remediation of node-tar vulnerabilities CVE-2021-32803 and CVE-2021-32804. Subsequent internal security review of node-tar and additional external bounty reports have resulted in another 5 CVE being remediated in core npm CLI dependencies including node-tar, and npm arborist.

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

  - c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)

  - nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930)

  - Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application     crashes due to missing input validation of host names returned by Domain Name Servers in Node.js dns     library which can lead to output of wrong hostnames (leading to Domain Hijacking) and injection     vulnerabilities in applications using the library. (CVE-2021-22931)

  - If the Node.js https API was used incorrectly and undefined was in passed for the rejectUnauthorized     parameter, no error was returned and connections to servers with an expired certificate would have been     accepted. (CVE-2021-22939)

  - Node.js before 16.6.1, 14.17.5, and 12.22.5 is vulnerable to a use after free attack where an attacker     might be able to exploit the memory corruption, to change process behavior. (CVE-2021-22940)

  - 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)

  - 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)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2021:3666 advisory.

  - nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930, CVE-2021-22940)

  - nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)

  - nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)

  - nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)

  - nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite     (CVE-2021-32803)

  - nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite     (CVE-2021-32804)

  - c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)

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

The remote CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CESA-2021:3666 advisory.

  - nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930, CVE-2021-22940)

  - nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)

  - nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)

  - nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)

  - nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite     (CVE-2021-32803)

  - nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite     (CVE-2021-32804)

  - c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)

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

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

  - c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)

  - nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930)

  - Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application     crashes due to missing input validation of host names returned by Domain Name Servers in Node.js dns     library which can lead to output of wrong hostnames (leading to Domain Hijacking) and injection     vulnerabilities in applications using the library. (CVE-2021-22931)

  - If the Node.js https API was used incorrectly and undefined was in passed for the rejectUnauthorized     parameter, no error was returned and connections to servers with an expired certificate would have been     accepted. (CVE-2021-22939)

  - Node.js before 16.6.1, 14.17.5, and 12.22.5 is vulnerable to a use after free attack where an attacker     might be able to exploit the memory corruption, to change process behavior. (CVE-2021-22940)

  - 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)

  - 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)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2021:3639 advisory.

  - libuv: out-of-bounds read in uv__idna_toascii() can lead to information disclosures or crashes     (CVE-2021-22918)

  - nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930, CVE-2021-22940)

  - nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)

  - nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)

  - nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)

  - nodejs-hosted-git-info: Regular Expression denial of service via shortcutMatch in fromUrl()     (CVE-2021-23362)

  - nodejs-ssri: Regular expression DoS (ReDoS) when parsing malicious SRI in strict mode (CVE-2021-27290)

  - nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite     (CVE-2021-32803)

  - nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite     (CVE-2021-32804)

  - c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2021:3638 advisory.

  - libuv: out-of-bounds read in uv__idna_toascii() can lead to information disclosures or crashes     (CVE-2021-22918)

  - nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930, CVE-2021-22940)

  - nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)

  - nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)

  - nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)

  - nodejs-hosted-git-info: Regular Expression denial of service via shortcutMatch in fromUrl()     (CVE-2021-23362)

  - nodejs-ssri: Regular expression DoS (ReDoS) when parsing malicious SRI in strict mode (CVE-2021-27290)

  - nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite     (CVE-2021-32803)

  - nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite     (CVE-2021-32804)

  - c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)

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

The remote CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CESA-2021:3623 advisory.

  - nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930, CVE-2021-22940)

  - nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)

  - nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)

  - nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)

  - nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite     (CVE-2021-32803)

  - nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite     (CVE-2021-32804)

  - c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2021:3623 advisory.

  - nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930, CVE-2021-22940)

  - nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)

  - nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)

  - nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)

  - nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite     (CVE-2021-32803)

  - nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite     (CVE-2021-32804)

  - c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)

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

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2021:3280 advisory.

  - nodejs-glob-parent: Regular expression denial of service (CVE-2020-28469)

  - nodejs-ini: Prototype pollution via malicious INI file (CVE-2020-7788)

  - nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930, CVE-2021-22940)

  - nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)

  - nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)

  - nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)

  - nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite     (CVE-2021-32803)

  - nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite     (CVE-2021-32804)

  - c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)

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

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2021:3281 advisory.

  - nodejs-glob-parent: Regular expression denial of service (CVE-2020-28469)

  - nodejs-ini: Prototype pollution via malicious INI file (CVE-2020-7788)

  - nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930, CVE-2021-22940)

  - nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)

  - nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)

  - nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)

  - nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite     (CVE-2021-32803)

  - nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite     (CVE-2021-32804)

  - c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)

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	Severity
161258	SUSE SLES15 Security Update : nodejs10 (SUSE-SU-2022:1717-1)	Nessus	SuSE Local Security Checks	critical
158636	openSUSE 15 Security Update : nodejs8 (openSUSE-SU-2022:0704-1)	Nessus	SuSE Local Security Checks	critical
158624	openSUSE 15 Security Update : nodejs14 (openSUSE-SU-2022:0715-1)	Nessus	SuSE Local Security Checks	critical
158621	SUSE SLES15 Security Update : nodejs8 (SUSE-SU-2022:0704-1)	Nessus	SuSE Local Security Checks	critical
158609	SUSE SLES15 Security Update : nodejs14 (SUSE-SU-2022:0715-1)	Nessus	SuSE Local Security Checks	critical
158577	openSUSE 15 Security Update : nodejs12 (openSUSE-SU-2022:0657-1)	Nessus	SuSE Local Security Checks	critical
158570	SUSE SLES15 Security Update : nodejs12 (SUSE-SU-2022:0657-1)	Nessus	SuSE Local Security Checks	critical
158433	SUSE SLES12 Security Update : nodejs14 (SUSE-SU-2022:0569-1)	Nessus	SuSE Local Security Checks	critical
158395	SUSE SLES12 Security Update : nodejs10 (SUSE-SU-2022:0570-1)	Nessus	SuSE Local Security Checks	critical
158357	SUSE SLES15 Security Update : nodejs8 (SUSE-SU-2022:0563-1)	Nessus	SuSE Local Security Checks	critical
158221	SUSE SLES12 Security Update : nodejs12 (SUSE-SU-2022:0531-1)	Nessus	SuSE Local Security Checks	critical
157829	Rocky Linux 8 : nodejs:14 (RLSA-2021:3666)	Nessus	Rocky Linux Local Security Checks	critical
157746	Rocky Linux 8 : nodejs:12 (RLSA-2021:3623)	Nessus	Rocky Linux Local Security Checks	critical
153819	FreeBSD : Node.js -- August 2021 Security Releases (2) (7062bce0-1b17-11ec-9d9d-0022489ad614)	Nessus	FreeBSD Local Security Checks	high
153765	Oracle Linux 8 : nodejs:14 (ELSA-2021-3666)	Nessus	Oracle Linux Local Security Checks	critical
153764	RHEL 8 : nodejs:14 (RHSA-2021:3666)	Nessus	Red Hat Local Security Checks	critical
153763	CentOS 8 : nodejs:14 (CESA-2021:3666)	Nessus	CentOS Local Security Checks	critical
153566	Oracle Linux 8 : nodejs:12 (ELSA-2021-3623)	Nessus	Oracle Linux Local Security Checks	critical
153553	RHEL 8 : nodejs:12 (RHSA-2021:3639)	Nessus	Red Hat Local Security Checks	critical
153552	RHEL 8 : nodejs:12 (RHSA-2021:3638)	Nessus	Red Hat Local Security Checks	critical
153532	CentOS 8 : nodejs:12 (CESA-2021:3623)	Nessus	CentOS Local Security Checks	critical
153524	RHEL 8 : nodejs:12 (RHSA-2021:3623)	Nessus	Red Hat Local Security Checks	critical
152863	RHEL 7 : rh-nodejs14-nodejs and rh-nodejs14-nodejs-nodemon (RHSA-2021:3280)	Nessus	Red Hat Local Security Checks	critical
152862	RHEL 7 : rh-nodejs12-nodejs and rh-nodejs12-nodejs-nodemon (RHSA-2021:3281)	Nessus	Red Hat Local Security Checks	critical

Detections

Analytics

CVE-2021-32804

high

Tenable Plugins

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

high

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical