p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in nodejs-current

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für nodejs-current: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 24

  1. CVE-2021-22883

    Hoch · CVSS 7.5EPSS 77,39%Korrektur verfügbar

    CVE-2021-22883

    Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 'unknownProtocol' are established. This leads to a leak of file descriptors. If a file descriptor limit is configured on the system, then the server is unable to accept new connections and prevent the process also from opening, e.g. a file. If no file descriptor limit is configured, then this lead to an excessive memory usage and cause the system to run out of memory.

    • Auf 15.10.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2021-22884

    Hoch · CVSS 7.5EPSS 36,84%Korrektur verfügbar

    CVE-2021-22884

    Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to DNS rebinding attacks as the whitelist includes “localhost6”. When “localhost6” is not present in /etc/hosts, it is just an ordinary domain that is resolved via DNS, i.e., over network. If the attacker controls the victim's DNS server or can spoof its responses, the DNS rebinding protection can be bypassed by using the “localhost6” domain. As long as the attacker uses the “localhost6” domain, they can still apply the attack described in CVE-2018-7160.

    • Auf 15.10.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2020-8265

    Hoch · CVSS 8.1EPSS 9,12%Korrektur verfügbar

    CVE-2020-8265

    Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an error, this object is passed back to the caller as part of a StreamWriteResult structure. This may be exploited to corrupt memory leading to a Denial of Service or potentially other exploits.

    • Auf 15.5.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2020-8287

    Mittel · CVSS 6.5EPSS 16,3%Korrektur verfügbar

    CVE-2020-8287

    Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-Encoding header fields). In this case, Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling.

    • Auf 15.5.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2020-8277

    Hoch · CVSS 7.5EPSS 54,16%Korrektur verfügbar

    CVE-2020-8277

    A Node.js application that allows an attacker to trigger a DNS request for a host of their choice could trigger a Denial of Service in versions < 15.2.1, < 14.15.1, and < 12.19.1 by getting the application to resolve a DNS record with a larger number of responses. This is fixed in 15.2.1, 14.15.1, and 12.19.1.

    • Auf 15.3.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2020-8201

    Hoch · CVSS 7.4EPSS 5,3%Korrektur verfügbar

    CVE-2020-8201

    Node.js < 12.18.4 and < 14.11 can be exploited to perform HTTP desync attacks and deliver malicious payloads to unsuspecting users. The payloads can be crafted by an attacker to hijack user sessions, poison cookies, perform clickjacking, and a multitude of other attacks depending on the architecture of the underlying system. The attack was possible due to a bug in processing of carrier-return symbols in the HTTP header names.

    • Auf 14.11.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2020-11080

    Niedrig · CVSS 3.7EPSS 5,32%Korrektur verfügbar

    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.

    • Auf 14.4.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2019-5737

    Hoch · CVSS 7.5EPSS 16,18%Korrektur verfügbar

    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.

    • Auf 11.10.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2018-12123

    Mittel · CVSS 4.3EPSS 4,03%Korrektur verfügbar

    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.

    • Auf 11.3.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2018-12122

    Hoch · CVSS 7.5EPSS 41,29%Korrektur verfügbar

    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.

    • Auf 11.3.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2018-12121

    Hoch · CVSS 7.5EPSS 10,21%Korrektur verfügbar

    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.

    • Auf 11.3.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2018-0734

    Mittel · CVSS 5.9EPSS 12,15%Korrektur verfügbar

    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).

    • Auf 11.3.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2018-0735

    Mittel · CVSS 5.9EPSS 4,72%Korrektur verfügbar

    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).

    • Auf 11.3.0-r0 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2018-7160

    Hoch · CVSS 8.8EPSS 9,49%Korrektur verfügbar

    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

    • Auf 9.10.0-r0 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →