rpm package
opensuse/nodejs10&distro=openSUSE Leap 15.0
pkg:rpm/opensuse/nodejs10&distro=openSUSE%20Leap%2015.0
Vulnerabilities (8)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2019-9518 | — | < 10.16.3-lp151.2.6.1 | 10.16.3-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 | — | < 10.16.3-lp151.2.6.1 | 10.16.3-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 | — | < 10.16.3-lp151.2.6.1 | 10.16.3-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 | — | < 10.16.3-lp151.2.6.1 | 10.16.3-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 | — | < 10.16.3-lp151.2.6.1 | 10.16.3-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 | — | < 10.16.3-lp151.2.6.1 | 10.16.3-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 | — | < 10.16.3-lp151.2.6.1 | 10.16.3-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 | — | < 10.16.3-lp151.2.6.1 | 10.16.3-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-9518Aug 13, 2019affected < 10.16.3-lp151.2.6.1fixed 10.16.3-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 < 10.16.3-lp151.2.6.1fixed 10.16.3-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 < 10.16.3-lp151.2.6.1fixed 10.16.3-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 < 10.16.3-lp151.2.6.1fixed 10.16.3-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 < 10.16.3-lp151.2.6.1fixed 10.16.3-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 < 10.16.3-lp151.2.6.1fixed 10.16.3-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 < 10.16.3-lp151.2.6.1fixed 10.16.3-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 < 10.16.3-lp151.2.6.1fixed 10.16.3-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