nginx: CVE-2019-9511 CVE-2019-9513 CVE-2019-9516

Debian Bug report logs - #935037
nginx: CVE-2019-9511 CVE-2019-9513 CVE-2019-9516

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: nginx: CVE-2019-9511 CVE-2019-9513 CVE-2019-9516

Date: Sun, 18 Aug 2019 14:31:05 +0200

Source: nginx
Version: 1.14.2-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1.10.3-1+deb9u2
Control: found -1 1.10.3-1

Hi,

The following vulnerabilities were published for nginx.

CVE-2019-9511[0]:
| 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 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.


CVE-2019-9513[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 consume excess CPU.


CVE-2019-9516[2]:
| 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 allocate memory for these headers and keep the
| allocation alive until the session dies. This can consume excess
| memory.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-9511
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9511
    https://github.com/nginx/nginx/commit/a987f81dd19210bc30b62591db331e31d3d74089
[1] https://security-tracker.debian.org/tracker/CVE-2019-9513
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9513
    https://github.com/nginx/nginx/commit/5ae726912654da10a9a81b2c8436829f3e94f69f
[2] https://security-tracker.debian.org/tracker/CVE-2019-9516
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9516
    https://github.com/nginx/nginx/commit/6dfbc8b1c2116f362bb871efebbf9df576738e89
[3] https://www.nginx.com/blog/nginx-updates-mitigate-august-2019-http-2-vulnerabilities/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Send a report that this bug log contains spam.