Page 3 of 27 results (0.004 seconds)

CVSS: 9.0EPSS: 1%CPEs: 3EXPL: 0

15 Aug 2023 — A vulnerability has been discovered in Node.js version 20, specifically within the experimental permission model. This flaw relates to improper handling of Buffers in file system APIs causing a traversal path to bypass when verifying file permissions. This vulnerability affects all users using the experimental permission model in Node.js 20. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js. Se ha descubierto una vulnerabilidad en Node.js versión 20... • https://hackerone.com/reports/2038134 • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •

CVSS: 9.0EPSS: 1%CPEs: 5EXPL: 0

15 Aug 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, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js. El uso de 'module.constructor.createRequire()' puede omitir el mecanismo de políticas y requerir módulos fuera de la definici... • https://hackerone.com/reports/2043807 • CWE-213: Exposure of Sensitive Information Due to Incompatible Policies •

CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0

31 Jul 2023 — 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: v16, v18 and, v20. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js El uso de __proto__ en process.mainModule.__proto__.require() puede omitir el mecanismo de políticas y requerir módulos fuera de la de... • https://nodejs.org/en/blog/vulnerability/june-2023-security-releases •

CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0

31 Jul 2023 — The generateKeys() API function returned from crypto.createDiffieHellman() only generates missing (or outdated) keys, that is, it only generates a private key if none has been set yet, but the function is also needed to compute the corresponding public key after calling setPrivateKey(). However, the documentation says this API call: "Generates private and public Diffie-Hellman key values". The documented behavior is very different from the actual behavior, and this difference could easily lead to security i... • https://lists.debian.org/debian-lts-announce/2024/03/msg00029.html •

CVSS: 5.3EPSS: 0%CPEs: 3EXPL: 0

31 Jul 2023 — 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. Cuando se ut... • https://nodejs.org/en/blog/vulnerability/june-2023-security-releases •

CVSS: 7.8EPSS: 0%CPEs: 1EXPL: 0

30 Jun 2023 — A privilege escalation vulnerability exists in Node.js 20 that allowed loading arbitrary OpenSSL engines when the experimental permission model is enabled, which can bypass and/or disable the permission model. The attack complexity is high. However, the crypto.setEngine() API can be used to bypass the permission model when called with a compatible OpenSSL engine. The OpenSSL engine can, for example, disable the permission model in the host process by manipulating the process's stack memory to locate the per... • https://hackerone.com/reports/1954535 • CWE-862: Missing Authorization •

CVSS: 7.8EPSS: 9%CPEs: 5EXPL: 1

30 Jun 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 RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20 A vulnerability has been identified in the Node.js, where llhttp parser in the http module in Node.j... • https://hackerone.com/reports/2001873 •