QID 355624

the use of proto in process.mainmodule.proto.require() can bypass the policy mechanism and require modules outside of the policy.json definition. this vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. please note that at the time this( CVE was issued, the policy is an experimental feature of node.js. (
( CVE-2023-30581) when an invalid public key is used to create an x509 certificate using the crypto.
X509certificate() api a non-expect termination occurs making it susceptible to dos attacks when the attacker could force interruptions of application processing, as the process terminates when accessing public key info of provided certificates from user code.
The current context of the users will be gone, and that will cause a dos scenario. this vulnerability affects all active node.js versions v16, v18, and, v20. (
( CVE-2023-30588) the llhttp parser 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). 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 vulnerability impacts all node.js active versions: v16, v18, and, v20. (
This change applies to all node.js active versions: v16, v18, and, v20. (
( CVE-2023-30590)

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.