rpm package
suse/nodejs18&distro=SUSE Linux Enterprise Module for Web and Scripting 15 SP5
pkg:rpm/suse/nodejs18&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Web%20and%20Scripting%2015%20SP5
Vulnerabilities (31)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-45143 | Low | 3.9 | < 18.18.2-150400.9.15.1 | 18.18.2-150400.9.15.1 | Oct 12, 2023 | Undici is an HTTP/1.1 client written from scratch for Node.js. Prior to version 5.26.2, Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Cookie` headers. By design, `cookie` headers are forbidden request headers, disallowing them to be se | |
| CVE-2023-44487 | Hig | 7.5 | KEV | < 18.18.2-150400.9.15.1 | 18.18.2-150400.9.15.1 | Oct 10, 2023 | The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023. |
| CVE-2023-32559 | Hig | 7.5 | < 18.17.1-150400.9.12.1 | 18.17.1-150400.9.12.1 | Aug 24, 2023 | A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. The use of the deprecated API `process.binding()` can bypass the policy mechanism by requiring internal modules and eventually take advantage of `pr | |
| CVE-2023-32002 | Cri | 9.8 | < 18.17.1-150400.9.12.1 | 18.17.1-150400.9.12.1 | Aug 21, 2023 | The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note | |
| CVE-2023-32006 | Hig | 8.8 | < 18.17.1-150400.9.12.1 | 18.17.1-150400.9.12.1 | Aug 15, 2023 | The use of `module.constructor.createRequire()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x, and | |
| CVE-2023-30589 | Hig | 7.5 | < 18.16.1-150400.9.9.1 | 18.16.1-150400.9.9.1 | Jul 1, 2023 | 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 RF | |
| CVE-2023-32067 | Hig | 7.5 | < 18.16.1-150400.9.9.1 | 18.16.1-150400.9.9.1 | May 25, 2023 | 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 lengt | |
| CVE-2023-31147 | Med | 5.9 | < 18.16.1-150400.9.9.1 | 18.16.1-150400.9.9.1 | May 25, 2023 | 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 ra | |
| CVE-2023-31130 | Med | 4.1 | < 18.16.1-150400.9.9.1 | 18.16.1-150400.9.9.1 | May 25, 2023 | 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 | |
| CVE-2023-31124 | Low | 3.7 | < 18.16.1-150400.9.9.1 | 18.16.1-150400.9.9.1 | May 25, 2023 | 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 | |
| CVE-2022-25881 | Med | 5.3 | < 18.16.1-150400.9.9.1 | 18.16.1-150400.9.9.1 | Jan 31, 2023 | 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. |
- affected < 18.18.2-150400.9.15.1fixed 18.18.2-150400.9.15.1
Undici is an HTTP/1.1 client written from scratch for Node.js. Prior to version 5.26.2, Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Cookie` headers. By design, `cookie` headers are forbidden request headers, disallowing them to be se
- affected < 18.18.2-150400.9.15.1fixed 18.18.2-150400.9.15.1
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
- affected < 18.17.1-150400.9.12.1fixed 18.17.1-150400.9.12.1
A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. The use of the deprecated API `process.binding()` can bypass the policy mechanism by requiring internal modules and eventually take advantage of `pr
- affected < 18.17.1-150400.9.12.1fixed 18.17.1-150400.9.12.1
The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note
- affected < 18.17.1-150400.9.12.1fixed 18.17.1-150400.9.12.1
The use of `module.constructor.createRequire()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x, and
- affected < 18.16.1-150400.9.9.1fixed 18.16.1-150400.9.9.1
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 RF
- affected < 18.16.1-150400.9.9.1fixed 18.16.1-150400.9.9.1
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 lengt
- affected < 18.16.1-150400.9.9.1fixed 18.16.1-150400.9.9.1
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 ra
- affected < 18.16.1-150400.9.9.1fixed 18.16.1-150400.9.9.1
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
- affected < 18.16.1-150400.9.9.1fixed 18.16.1-150400.9.9.1
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
- affected < 18.16.1-150400.9.9.1fixed 18.16.1-150400.9.9.1
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.
Page 2 of 2