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: 34

  1. CVE-2021-44533

    Mittel · CVSS 5.3EPSS 9,36%Korrektur verfügbar

    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

    • Auf 17.3.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2021-44532

    Mittel · CVSS 5.3EPSS 10,36%Korrektur verfügbar

    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.

    • Auf 17.3.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2021-44531

    Hoch · CVSS 7.4EPSS 8,37%Korrektur verfügbar

    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.

    • Auf 17.3.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2022-21824

    Hoch · CVSS 8.2EPSS 21,51%Korrektur verfügbar

    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.

    • Auf 17.3.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2021-3672

    Mittel · CVSS 5.6EPSS 2,81%Korrektur verfügbar

    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.

    • Auf 16.6.2-r0 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2021-22931

    Kritisch · CVSS 9.8EPSS 21,95%Korrektur verfügbar

    CVE-2021-22931

    Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation of host names returned by Domain Name Servers in Node.js dns library which can lead to output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library.

    • Auf 16.6.2-r0 aktualisieren
    Veröffentlicht Aktualisiert
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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

Prüfen Sie Ihren Server

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

Prüfen Sie Ihren Server →