The remote SUSE Linux SLES12 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2023:2662-1 advisory.

  - This affects versions of the package http-cache-semantics before 4.1.1. The issue can be exploited via     malicious request header values sent to a server, when that server reads the cache policy from the request     using this library. (CVE-2022-25881)

  - The vulnerability exists due to the use of proto in process.mainModule.proto.require(). This allows to     bypass the policy mechanism and require modules outside of the policy.json definition. (CVE-2023-30581)

  - The vulnerability exists due to the way Node.js (.msi version) installation process handles a missing     %USERPROFILE% environment variable. If the variable is not set, the .msi installer will try to include a     current working directory into the search path and will libraries in an unsafe manner. A local user can     place a malicious file on the victim's system and execute arbitrary code with elevated privileges.
    (CVE-2023-30585)

  - The vulnerability exists due to insufficient validation of user-supplied public key within the     crypto.X509Certificate() API. A remote user can pass an invalid public key to the application and perform     a denial of service (DoS) attack. (CVE-2023-30588)

  - The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit     HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient     to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence     should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20     (CVE-2023-30589)

  - The vulnerability exists due to inconsistency between implementation and documented design within the     generateKeys() API function. The documented behavior is different from the actual behavior, and this     difference could lead to security issues in applications that use these APIs as the DiffieHellman may be     used as the basis for application-level security. (CVE-2023-30590)

  - c-ares is an asynchronous resolver library. When cross-compiling c-ares and using the autotools build     system, CARES_RANDOM_FILE will not be set, as seen when cross compiling aarch64 android. This will     downgrade to using rand() as a fallback which could allow an attacker to take advantage of the lack of     entropy by not using a CSPRNG. This issue was patched in version 1.19.1. (CVE-2023-31124)

  - c-ares is an asynchronous resolver library. ares_inet_net_pton() is vulnerable to a buffer underflow for     certain ipv6 addresses, in particular 0::00:00:00/2 was found to cause an issue. C-ares only uses this     function internally for configuration purposes which would require an administrator to configure such an     address via ares_set_sortlist(). However, users may externally use ares_inet_net_pton() for other purposes     and thus be vulnerable to more severe issues. This issue has been fixed in 1.19.1. (CVE-2023-31130)

  - c-ares is an asynchronous resolver library. When /dev/urandom or RtlGenRandom() are unavailable, c-ares     uses rand() to generate random numbers used for DNS query ids. This is not a CSPRNG, and it is also not     seeded by srand() so will generate predictable output. Input from the random number generator is fed into     a non-compilant RC4 implementation and may not be as strong as the original RC4 implementation. No attempt     is made to look for modern OS-provided CSPRNGs like arc4random() that is widely available. This issue has     been fixed in version 1.19.1. (CVE-2023-31147)

  - c-ares is an asynchronous resolver library. c-ares is vulnerable to denial of service. If a target     resolver sends a query, the attacker forges a malformed UDP packet with a length of 0 and returns them to     the target resolver. The target resolver erroneously interprets the 0 length as a graceful shutdown of the     connection. This issue has been patched in version 1.19.1. (CVE-2023-32067)

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

Detections

Analytics

SUSE SLES12 Security Update : nodejs18 (SUSE-SU-2023:2662-1)

high Nessus Plugin ID 177699

Version 1.6

Version 1.5

Version 1.4

Version 1.2

Version 1.1

Version 1.0

Version 1.6 Dec 5, 2023, 2:37 PM CVSSv2 score source (changed from "CVE-2023-30589" to "CVE-2023-30590") Plugin Feed: 202312051437
Version 1.5 Aug 11, 2023, 10:11 AM IAVM reference Plugin Feed: 202308111011
Version 1.4 Jul 14, 2023, 10:50 AM Detection Plugin metadata Plugin Feed: 202307141050
Version 1.2 Jul 12, 2023, 2:16 PM CVSS metrics ("CVSSv2 score" changed from 6.4 to 7.8. "CVSSv3 score" changed from 6.5 to 7.5. "CVSSv2 vector" changed from "CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:N" to "CVSS2#AV:N/AC:L/Au:N/C:N/I:C/A:N". "CVSSv3 vector" changed from "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N" to "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N") CVSSv2 score source (changed from "CVE-2023-31147" to "CVE-2023-30589") CVSSv2 severity (based on CVE-2023-30589, severity increased from "Medium" to "High") CVSSv3 score source (set to "CVE-2023-30589") CVSSv3 severity (based on CVE-2023-30589, severity increased from "Medium" to "High") Plugin Feed: 202307121416
Version 1.1 Jun 30, 2023, 10:02 AM IAVM reference STIG Severity (set to "I") Plugin Feed: 202306301002
Version 1.0 Jun 28, 2023, 4:03 PM New Plugin Feed: 202306281603