p PatchFirst

PatchFirst · Latest vulnerabilities

nodejs-current vulnerabilities

Vulnerabilities published for nodejs-current in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 46

  1. CVE-2023-39333

    Medium · CVSS 5.3EPSS 1.11%Fix available

    CVE-2023-39333

    Maliciously crafted export names in an imported WebAssembly module can inject JavaScript code. The injected code may be able to access data and functions that the WebAssembly module itself does not have access to, similar to as if the WebAssembly module was a JavaScript module. This vulnerability affects users of any active release line of Node.js. The vulnerable feature is only available if Node.js is started with the `--experimental-wasm-modules` command line option.

    • Update to 20.8.1-r0
    Published Updated
  2. CVE-2023-39331

    High · CVSS 7.7EPSS 1.51%Fix available

    CVE-2023-39331

    A previously disclosed vulnerability (CVE-2023-30584) was patched insufficiently in commit 205f1e6. The new path traversal vulnerability arises because the implementation does not protect itself against the application overwriting built-in utility functions with user-defined implementations. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

    • Update to 20.8.1-r0
    Published Updated
  3. CVE-2023-38552

    High · CVSS 7.5EPSS 1.24%Fix available

    CVE-2023-38552

    When the Node.js policy feature checks the integrity of a resource against a trusted manifest, the application can intercept the operation and return a forged checksum to the node's policy implementation, thus effectively disabling the integrity check. Impacts: This vulnerability affects all users using the experimental policy mechanism in all active release lines: 18.x and, 20.x. Please note that at the time this CVE was issued, the policy mechanism is an experimental feature of Node.js.

    • Update to 20.8.1-r0
    Published Updated
  4. CVE-2023-39332

    Critical · CVSS 9.8EPSS 2.19%Fix available

    CVE-2023-39332

    Various `node:fs` functions allow specifying paths as either strings or `Uint8Array` objects. In Node.js environments, the `Buffer` class extends the `Uint8Array` class. Node.js prevents path traversal through strings (see CVE-2023-30584) and `Buffer` objects (see CVE-2023-32004), but not through non-`Buffer` `Uint8Array` objects. This is distinct from CVE-2023-32004 which only referred to `Buffer` objects. However, the vulnerability follows the same pattern using `Uint8Array` instead of `Buffer`. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

    • Update to 20.8.1-r0
    Published Updated
  5. CVE-2023-45143

    Low · CVSS 3.9EPSS 1.37%Fix available

    Undici's cookie header not cleared on cross-origin redirect in fetch

    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 set in RequestInit.headers in browser environments. Since undici handles headers more liberally than the spec, there was a disconnect from the assumptions the spec made, and undici's implementation of fetch. As such this may lead to accidental leakage of cookie to a third-party site or a malicious attacker who can control the redirection target (ie. an open redirector)

    • Update to 20.8.1-r0
    Published Updated
  6. CVE-2022-35255

    Critical · CVSS 9.1EPSS 2.13%Fix available

    CVE-2022-35255

    A weak randomness in WebCrypto keygen vulnerability exists in Node.js 18 due to a change with EntropySource() in SecretKeyGenTraits::DoKeyGen() in src/crypto/crypto_keygen.cc. There are two problems with this: 1) It does not check the return value, it assumes EntropySource() always succeeds, but it can (and sometimes will) fail. 2) The random data returned byEntropySource() may not be cryptographically strong and therefore not suitable as keying material.

    • Update to 18.9.1-r0
    Published Updated
  7. CVE-2022-32222

    Medium · CVSS 5.3EPSS 2.19%Fix available

    CVE-2022-32222

    A cryptographic vulnerability exists on Node.js on linux in versions of 18.x prior to 18.40.0 which allowed a default path for openssl.cnf that might be accessible under some circumstances to a non-admin user instead of /etc/ssl as was the case in versions prior to the upgrade to OpenSSL 3.

    • Update to 18.6.0-r0
    • Update to 18.9.1-r0
    Published Updated
  8. CVE-2022-32212

    High · CVSS 8.1EPSS 6.43%Fix available

    CVE-2022-32212

    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.

    • Update to 18.6.0-r0
    Published Updated
  9. CVE-2021-44533

    Medium · CVSS 5.3EPSS 9.36%Fix available

    CVE-2021-44533

    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 vulnerab

    • Update to 17.3.1-r0
    Published Updated
  10. CVE-2021-44532

    Medium · CVSS 5.3EPSS 10.36%Fix available

    CVE-2021-44532

    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.

    • Update to 17.3.1-r0
    Published Updated
  11. CVE-2021-44531

    High · CVSS 7.4EPSS 8.37%Fix available

    CVE-2021-44531

    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.

    • Update to 17.3.1-r0
    Published Updated
  12. CVE-2022-21824

    High · CVSS 8.2EPSS 21.51%Fix available

    CVE-2022-21824

    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.

    • Update to 17.3.1-r0
    Published Updated
  13. CVE-2021-3672

    Medium · CVSS 5.6EPSS 2.81%Fix available

    CVE-2021-3672

    A flaw was found in c-ares library, where a missing input validation check of host names returned by DNS (Domain Name Servers) can lead to output of wrong hostnames which might potentially lead to Domain Hijacking. The highest threat from this vulnerability is to confidentiality and integrity as well as system availability.

    • Update to 16.6.2-r0
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →