Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This notice regards the following CVEs:

The issues mentioned above refer to several names and versions of NuGet packages containing vulnerable DLL libraries, along with the NuGet package versions containing a fixed DLL library. However, according to their SHA-1 identifiers, some of the vulnerable DLL libraries still exist in other directories of the fixed NuGet packages. Therefore, the fixed version for each NuGet package refers to a package that isn'tunconditionally vulnerable, but ispotentially vulnerable depending on the specifications of the run-time environment.

...

  • CVE-2019-9511 “Data Dribble”: The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.
    CVSS 3.x Score7.5 HIGH

  • CVE-2019-9512 “Ping Flood”: 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 consume excess CPU, memory, or both, potentially leading to a denial of service.
    CVSS 3.x Score7.5 HIGH

  • CVE-2019-9513 “Resource Loop”: 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 consume excess CPU, potentially leading to a denial of service.
    CVSS 3.x Score7.5 HIGH

  • CVE-2019-9514 “Reset Flood”: 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 queues the RST_STREAM frames, this can consume excess memory, CPU, or both, potentially leading to a denial of service.
    CVSS 3.x Score7.5 HIGH

  • CVE-2019-9515 “Settings Flood”: 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 is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.
    CVSS 3.x Score7.5 HIGH

  • CVE-2019-9516 “0-Length Headers Leak”: 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 allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory, potentially leading to a denial of service.
    CVSS 3.x Score7.5 HIGH

  • CVE-2019-9517 “Internal Data Buffering”: 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 write (many of) the bytes on the wire. The attacker then sends a stream of requests for a large response object. Depending on how the servers queue the responses, this can consume excess memory, CPU, or both, potentially leading to a denial of service.
    CVSS 3.x Score7.5 HIGH

  • CVE-2019-9518 “Empty Frames Flood”: 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. The peer spends time processing each frame disproportionate to attack bandwidth. This can consume excess CPU, potentially leading to a denial of service.
    CVSS 3.x Score7.5 HIGH

Vulnerable Projects

Project

Vulnerabilities

Vulnerable Versions

Mitigation

Apache Traffic Server

CVE-2019-9511, CVE-2019-9512, CVE-2019-9513, CVE-2019-9514, CVE-2019-9515, CVE-2019-9516, CVE-2019-9517, CVE-2019-9518.

6.x: 6.0 - 6.2.3
7.x: 7.0 - 7.1.6
8.x: 8.0 -  8.1.3

6.x: No fix available.
7.x: Upgrade to 7.1.7 (patch).
8.x: Upgrade to 8.1.4 (patch).

Go

CVE-2019-9512, CVE-2019-9514. Official Website Advisory

1.11.x: 1.11.0 - 1.11.12
1.12.x: 1.12.0 - 1.12.7

1.11.x: Upgrade to 1.11.13 (patch).
1.12.x: Upgrade to 1.12.8 (patch).

H2O

CVE-2019-9512, CVE-2019-9514, CVE-2019-9515. Official Website Advisory

2.2.x: 2.2.0 - 2.2.5
2.3.x: 2.3.0-beta1

2.2.x: Upgrade to 2.2.6 (patch).
2.3.x: Upgrade to 2.3.0-beta2 (patch).

Eclipse Jetty

CVE-2019-9511, CVE-2019-9512, CVE-2019-9513, CVE-2019-9514, CVE-2019-9515, CVE-2019-9516, CVE-2019-9517, CVE-2019-9518. Official Website Advisory

9.3.x - 9.4.20

Upgrade to 9.4.21 (patch).

Netty

CVE-2019-9512, CVE-2019-9514, CVE-2019-9515, CVE-2019-9518. Official Website Advisory

4.1.0-beta4 - 4.1.38

Upgrade to 4.1.39 (patch-1 [9512, 9514, 9515], patch-2 [9518]).

Nghttp2

CVE-2019-9511, CVE-2019-9513. Official Website Advisory

0.1.0 - 1.39.1

Upgrade to 1.39.2 (patch-1patch-2).

NGINX

CVE-2019-9511, CVE-2019-9513, CVE-2019-9516. Official Website Advisory

NOTE: The releases (X.Y.Z) splitted into two types: if Y is divisible by 2 - stable, otherwise - mainline.
Stable: 0.2.x - 1.16.0
Mainline:  0.1.x - 1.17.2

Stable: Upgrade to 1.16.1 (patch-1 [9511], patch-2 [9513], patch-3 [9516]).
Mainline: Upgrade to 1.17.3 (patch-1 [9511], patch-2 [9513], patch-3 [9516]).

NodeJS

CVE-2019-9511, CVE-2019-9512, CVE-2019-9513, CVE-2019-9514, CVE-2019-9515, CVE-2019-9516, CVE-2019-9517, CVE-2019-9518. Official Website Advisory

8.x: 8.0.0 - 8.16.0
10.x: 10.0.0 - 1.16.2
12.x: 12.0.0 - 12.8.0 

8.x: Upgrade to 8.16.1 (patch-1 [9511, 9517], patch-2 [9511, 9517], patch-3 [9512, 9515], patch-4 [9512, 9515], patch-5 [9513], patch-6 [9513], patch-7 [9514], patch-8 [9514], patch-9 [9516], patch-10 [9518]).
10.x: Upgrade to 10.16.3 (patch-1 [9511, 9517], patch-2 [9511, 9517], patch-3 [9512, 9515], patch-4 [9512, 9515], patch-5 [9513], patch-6 [9513], patch-7 [9514], patch-8 [9514], patch-9 [9516], patch-10 [9518]).
12.x: Upgrade to 12.8.1 (patch-1 [9511, 9517], patch-2 [9511, 9517], patch-3 [9512, 9515], patch-4 [9512, 9515], patch-5 [9513], patch-6 [9513], patch-7 [9514], patch-8 [9514], patch-9 [9516], patch-10 [9518]).

.Net Packages with no Vulnerable Code

...