p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de nodejs-current

Vulnérabilité publiée pour nodejs-current au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 17

  1. CVE-2020-11080

    Faible · CVSS 3.7EPSS 5,32%Correctif disponible

    Denial of service in nghttp2

    In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection.

    • Mettez à jour vers 14.4.0-r0
    Publication Mise à jour
  2. CVE-2019-5737

    Élevée · CVSS 7.5EPSS 16,18%Correctif disponible

    CVE-2019-5737

    In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1, an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly. This keeps the connection and associated resources alive for a long period of time. Potential attacks are mitigated by the use of a load balancer or other proxy layer. This vulnerability is an extension of CVE-2018-12121, addressed in November and impacts all active Node.js release lines including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1.

    • Mettez à jour vers 11.10.1-r0
    Publication Mise à jour
  3. CVE-2018-12123

    Moyenne · CVSS 4.3EPSS 4,03%Correctif disponible

    CVE-2018-12123

    Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Hostname spoofing in URL parser for javascript protocol: If a Node.js application is using url.parse() to determine the URL hostname, that hostname can be spoofed by using a mixed case "javascript:" (e.g. "javAscript:") protocol (other protocols are not affected). If security decisions are made about the URL based on the hostname, they may be incorrect.

    • Mettez à jour vers 11.3.0-r0
    Publication Mise à jour
  4. CVE-2018-12122

    Élevée · CVSS 7.5EPSS 41,29%Correctif disponible

    CVE-2018-12122

    Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Slowloris HTTP Denial of Service: An attacker can cause a Denial of Service (DoS) by sending headers very slowly keeping HTTP or HTTPS connections and associated resources alive for a long period of time.

    • Mettez à jour vers 11.3.0-r0
    Publication Mise à jour
  5. CVE-2018-12121

    Élevée · CVSS 7.5EPSS 10,21%Correctif disponible

    CVE-2018-12121

    Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Denial of Service with large HTTP headers: By using a combination of many requests with maximum sized headers (almost 80 KB per connection), and carefully timed completion of the headers, it is possible to cause the HTTP server to abort from heap allocation failure. Attack potential is mitigated by the use of a load balancer or other proxy layer.

    • Mettez à jour vers 11.3.0-r0
    Publication Mise à jour
  6. CVE-2018-0734

    Moyenne · CVSS 5.9EPSS 12,15%Correctif disponible

    Timing attack against DSA

    The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

    • Mettez à jour vers 11.3.0-r0
    Publication Mise à jour
  7. CVE-2018-0735

    Moyenne · CVSS 5.9EPSS 4,72%Correctif disponible

    Timing attack against ECDSA signature generation

    The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.1.1a (Affected 1.1.1).

    • Mettez à jour vers 11.3.0-r0
    Publication Mise à jour
  8. CVE-2018-7160

    Élevée · CVSS 8.8EPSS 9,49%Correctif disponible

    CVE-2018-7160

    The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to

    • Mettez à jour vers 9.10.0-r0
    Publication Mise à jour
  9. CVE-2018-7159

    Moyenne · CVSS 5.3EPSS 3,54%Correctif disponible

    CVE-2018-7159

    The HTTP parser in all current versions of Node.js ignores spaces in the `Content-Length` header, allowing input such as `Content-Length: 1 2` to be interpreted as having a value of `12`. The HTTP specification does not allow for spaces in the `Content-Length` value and the Node.js HTTP parser has been brought into line on this particular difference. The security risk of this flaw to Node.js users is considered to be VERY LOW as it is difficult, and may be impossible, to craft an attack that makes use of this flaw in a way that could not already be achieved by supplying an incorrect value for `Content-Length`. Vulnerabilities may exist in use

    • Mettez à jour vers 9.10.0-r0
    Publication Mise à jour
  10. CVE-2018-7158

    Élevée · CVSS 7.5EPSS 3,45%Correctif disponible

    CVE-2018-7158

    The `'path'` module in the Node.js 4.x release line contains a potential regular expression denial of service (ReDoS) vector. The code in question was replaced in Node.js 6.x and later so this vulnerability only impacts all versions of Node.js 4.x. The regular expression, `splitPathRe`, used within the `'path'` module for the various path parsing functions, including `path.dirname()`, `path.extname()` and `path.parse()` was structured in such a way as to allow an attacker to craft a string, that when passed through one of these functions, could take a significant amount of time to evaluate, potentially leading to a full denial of service.

    • Mettez à jour vers 9.10.0-r0
    Publication Mise à jour
  11. CVE-2017-15897

    Faible · CVSS 3.1EPSS 2,32%Correctif disponible

    CVE-2017-15897

    Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, 'Buffer.alloc(0x100, "This is not correctly encoded", "hex");' The buffer implementation was updated such that the buffer will be initialized to all zeros in these cases.

    • Mettez à jour vers 9.2.1-r0
    Publication Mise à jour
  12. CVE-2017-15896

    Critique · CVSS 9.1EPSS 2,38%Correctif disponible

    CVE-2017-15896

    Node.js was affected by OpenSSL vulnerability CVE-2017-3737 in regards to the use of SSL_read() due to TLS handshake failure. The result was that an active network attacker could send application data to Node.js using the TLS or HTTP2 modules in a way that bypassed TLS authentication and encryption.

    • Mettez à jour vers 9.2.1-r0
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →