rpm package
opensuse/nodejs8&distro=openSUSE Leap 15.0
pkg:rpm/opensuse/nodejs8&distro=openSUSE%20Leap%2015.0
Vulnerabilities (13)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2019-9518 | — | < 8.16.1-lp151.2.6.1 | 8.16.1-lp151.2.6.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to a flood of empty frames, potentially leading to a denial of service. The attacker sends a stream of frames with an empty payload and without the end-of-stream flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE. | ||
| CVE-2019-9517 | — | < 8.16.1-lp151.2.6.1 | 8.16.1-lp151.2.6.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering, potentially leading to a denial of service. The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually writ | ||
| CVE-2019-9516 | — | < 8.16.1-lp151.2.6.1 | 8.16.1-lp151.2.6.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service. The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations a | ||
| CVE-2019-9515 | — | < 8.16.1-lp151.2.6.1 | 8.16.1-lp151.2.6.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame | ||
| CVE-2019-9513 | — | < 8.16.1-lp151.2.6.1 | 8.16.1-lp151.2.6.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consu | ||
| CVE-2019-9512 | — | < 8.16.1-lp151.2.6.1 | 8.16.1-lp151.2.6.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consum | ||
| CVE-2019-9511 | — | < 8.16.1-lp151.2.6.1 | 8.16.1-lp151.2.6.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and | ||
| CVE-2019-9514 | — | < 8.16.1-lp151.2.6.1 | 8.16.1-lp151.2.6.1 | Aug 13, 2019 | Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer | ||
| CVE-2019-13173 | — | < 8.15.1-lp151.2.3.1 | 8.15.1-lp151.2.3.1 | Jul 2, 2019 | fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system's file with the contents of the extracted file. The fstream.DirW | ||
| CVE-2018-12123 | — | < 8.15.0-lp150.2.9.1 | 8.15.0-lp150.2.9.1 | Nov 28, 2018 | 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. | ||
| CVE-2018-12122 | — | < 8.15.0-lp150.2.9.1 | 8.15.0-lp150.2.9.1 | Nov 28, 2018 | 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. | ||
| CVE-2018-12121 | — | < 8.15.0-lp150.2.9.1 | 8.15.0-lp150.2.9.1 | Nov 28, 2018 | 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 | ||
| CVE-2018-12116 | — | < 8.15.0-lp150.2.9.1 | 8.15.0-lp150.2.9.1 | Nov 28, 2018 | Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be convinced to use unsanitized user-provided Unicode data for the `path` option of an HTTP request, then data can be provided which will trigger a second, unexpected, and user-define |
- CVE-2019-9518Aug 13, 2019affected < 8.16.1-lp151.2.6.1fixed 8.16.1-lp151.2.6.1
Some HTTP/2 implementations are vulnerable to a flood of empty frames, potentially leading to a denial of service. The attacker sends a stream of frames with an empty payload and without the end-of-stream flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE.
- CVE-2019-9517Aug 13, 2019affected < 8.16.1-lp151.2.6.1fixed 8.16.1-lp151.2.6.1
Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering, potentially leading to a denial of service. The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually writ
- CVE-2019-9516Aug 13, 2019affected < 8.16.1-lp151.2.6.1fixed 8.16.1-lp151.2.6.1
Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service. The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations a
- CVE-2019-9515Aug 13, 2019affected < 8.16.1-lp151.2.6.1fixed 8.16.1-lp151.2.6.1
Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame
- CVE-2019-9513Aug 13, 2019affected < 8.16.1-lp151.2.6.1fixed 8.16.1-lp151.2.6.1
Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consu
- CVE-2019-9512Aug 13, 2019affected < 8.16.1-lp151.2.6.1fixed 8.16.1-lp151.2.6.1
Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consum
- CVE-2019-9511Aug 13, 2019affected < 8.16.1-lp151.2.6.1fixed 8.16.1-lp151.2.6.1
Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and
- CVE-2019-9514Aug 13, 2019affected < 8.16.1-lp151.2.6.1fixed 8.16.1-lp151.2.6.1
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer
- CVE-2019-13173Jul 2, 2019affected < 8.15.1-lp151.2.3.1fixed 8.15.1-lp151.2.3.1
fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system's file with the contents of the extracted file. The fstream.DirW
- CVE-2018-12123Nov 28, 2018affected < 8.15.0-lp150.2.9.1fixed 8.15.0-lp150.2.9.1
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.
- CVE-2018-12122Nov 28, 2018affected < 8.15.0-lp150.2.9.1fixed 8.15.0-lp150.2.9.1
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.
- CVE-2018-12121Nov 28, 2018affected < 8.15.0-lp150.2.9.1fixed 8.15.0-lp150.2.9.1
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
- CVE-2018-12116Nov 28, 2018affected < 8.15.0-lp150.2.9.1fixed 8.15.0-lp150.2.9.1
Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be convinced to use unsanitized user-provided Unicode data for the `path` option of an HTTP request, then data can be provided which will trigger a second, unexpected, and user-define