This update for nodejs10 fixes the following issues :

  - nodejs10 was updated to 10.22.1 LTS :

  - CVE-2020-8252: Fixed a buffer overflow in realpath     (bsc#1176589).

  - CVE-2020-15095: Fixed an information leak through log     files (bsc#1173937).

  - Explicitly add -fno-strict-aliasing to CFLAGS to fix     compilation on Aarch64 with gcc10 (bsc#1172686)&#9; 

This update was imported from the SUSE:SLE-15:Update update project.

The remote host is affected by the vulnerability described in GLSA-202101-07 (NodeJS: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in NodeJS. Please review       the CVE identifiers referenced below for details.
  Impact :

    Please review the referenced CVE identifiers for details.
  Workaround :

    There is no known workaround at this time.

The Rocky Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ crlsa-2020_4272 advisory.

    * nodejs-dot-prop: prototype pollution (CVE-2020-8116)

    * nodejs: HTTP request smuggling due to CR-to-Hyphen conversion (CVE-2020-8201)

    * npm: Sensitive information exposure through logs (CVE-2020-15095)

    * libuv: buffer overflow in realpath (CVE-2020-8252)

Tenable has extracted the preceding description block directly from the CIQ 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 CentOS Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the nodejs-16.16.0-1.el9 build changelog.

  - Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through     log files. The CLI supports URLs like     <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>. The password value is not redacted     and is printed to stdout and also to any generated log files. (CVE-2020-15095)

  - 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 parser in accepts requests with a space (SP) right after the header name before the colon. This can     lead to HTTP Request Smuggling (HRS) in llhttp < v2.1.4 and < v6.0.6. (CVE-2021-22959)

  - The parse function in llhttp < 2.1.4 and < 6.0.6. ignores chunk extensions when parsing the body of     chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions. (CVE-2021-22960)

  - ssri 5.2.2-8.0.0, fixed in 8.0.1, processes SRIs using a regular expression which is vulnerable to a     denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of     service. This issue only affects consumers using the strict option. (CVE-2021-27290)

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

  - The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency     information in package-lock.json differs from package.json. This behavior is inconsistent with the     documentation, and makes it easier for attackers to install malware that was supposed to have been blocked     by an exact version match requirement in package-lock.json. NOTE: The npm team believes this is not a     vulnerability. It would require someone to socially engineer package.json which has different dependencies     than package-lock.json. That user would have to have file system or write access to change dependencies.
    The npm team states preventing malicious actors from socially engineering or gaining file system access is     outside the scope of the npm CLI. (CVE-2021-43616)

  - Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a     particular SAN type, can result in bypassing name-constrained intermediates. Node.js < 12.22.9, < 14.18.3,     < 16.13.2, and < 17.3.1 was accepting URI SAN types, which PKIs are often not defined to use.
    Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.Versions of Node.js     with the fix for this disable the URI SAN type when checking a certificate against a hostname. This     behavior can be reverted through the --security-revert command-line option. (CVE-2021-44531)

  - Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 converts SANs (Subject Alternative Names) to a     string format. It uses this string to check peer certificates against hostnames when validating     connections. The string format was subject to an injection vulnerability when name constraints were used     within a certificate chain, allowing the bypass of these name constraints.Versions of Node.js with the fix     for this escape SANs containing the problematic characters in order to prevent the injection. This     behavior can be reverted through the --security-revert command-line option. (CVE-2021-44532)

  - Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished     Names correctly. Attackers could craft certificate subjects containing a single-value Relative     Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in     order to inject a Common Name that would allow bypassing the certificate subject verification.Affected     versions of Node.js that do not accept multi-value Relative Distinguished Names and are thus not     vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation     of certificate subjects may be vulnerable. (CVE-2021-44533)

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

  - A OS Command Injection vulnerability exists in Node.js versions <14.20.0, <16.20.0, <18.5.0 due to an     insufficient IsAllowedHost check that can easily be bypassed because IsIPAddress does not properly check     if an IP address is invalid before making DBS requests allowing rebinding attacks. (CVE-2022-32212)

  - The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly parse     and validate Transfer-Encoding headers and can lead to HTTP Request Smuggling (HRS). (CVE-2022-32213)

  - The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use     the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).
    (CVE-2022-32214)

  - The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly     handle multi-line Transfer-Encoding headers. This can lead to HTTP Request Smuggling (HRS).
    (CVE-2022-32215)

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

The Rocky Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ crlsa-2021_0548 advisory.

    * libuv: buffer overflow in realpath (CVE-2020-8252)

    * nodejs-npm-user-validate: improper input validation when validating user emails leads to ReDoS     (CVE-2020-7754)

    * nodejs-y18n: prototype pollution vulnerability (CVE-2020-7774)

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

    * nodejs-dot-prop: prototype pollution (CVE-2020-8116)

    * nodejs: use-after-free in the TLS implementation (CVE-2020-8265)

    * npm: sensitive information exposure through logs (CVE-2020-15095)

    * nodejs-ajv: prototype pollution via crafted JSON schema in ajv.validate function (CVE-2020-15366)

    * nodejs-yargs-parser: prototype pollution vulnerability (CVE-2020-7608)

    * nodejs: HTTP request smuggling via two copies of a header field in an http request (CVE-2020-8287)

Tenable has extracted the preceding description block directly from the CIQ 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 Rocky Linux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ ciqsa-2026_0466 advisory.

    This advisory aggregates security fixes for the nodejs SRPM in CIQ LTS 9.2. It addresses 56 CVEs:
    CVE-2021-3918, CVE-2019-9517, CVE-2023-24807, CVE-2023-44487, CVE-2023-23936, and 51 more.

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

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	Published	Updated	Severity
141411	openSUSE Security Update : nodejs10 (openSUSE-2020-1660)	Nessus	SuSE Local Security Checks	10/13/2020	2/15/2024	high
144864	GLSA-202101-07 : NodeJS: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	1/12/2021	1/30/2024	high
358721	Rocky Linux 8 [CIQ] Security Update: nodejs-nodemon / nodejs-packaging Multiple Vulnerabilities (crlsa-2020_4272)	Nessus	Rocky Linux Local Security Checks	10/1/2026	10/1/2026	high
191380	CentOS 9 : nodejs-16.16.0-1.el9	Nessus	CentOS Local Security Checks	2/29/2024	4/26/2024	critical
359206	Rocky Linux 8 [CIQ] Security Update: nodejs-nodemon / nodejs-packaging Multiple Vulnerabilities (crlsa-2021_0548)	Nessus	Rocky Linux Local Security Checks	10/1/2026	10/1/2026	critical
355900	Rocky Linux 9.2 [CIQ] Security Update: nodejs / nodejs-debuginfo / nodejs-debugsource / nodejs-docs / etc Multiple Vulnerabilities (ciqsa-2026_0466)	Nessus	Rocky Linux Local Security Checks	10/1/2026	10/13/2026	medium

Detections

Analytics

Plugins Search

high

high

high

critical

critical

medium