Summary
Package updates are available for Amazon Linux 2 that fix the following vulnerabilities: CVE-2019-6477: With pipelining enabled each incoming query on a TCP connection requires a similar resource allocation to a query received via UDP or via TCP without pipelining enabled. A client using a TCP-pipelined connection to a server could consume more resources than the server has been provisioned to handle. When a TCP connection with a large number of pipelined queries is closed, the load on the server releasing these multiple resources can cause it to become unresponsive, even for queries that can be answered authoritatively or from cache. (This is most likely to be perceived as an intermittent server problem). 1773617: CVE-2019-6477 bind: TCP Pipelining doesn't limit TCP clients on a single connection CVE-2019-6465: Controls for zone transfers may not be properly applied to Dynamically Loadable Zones (DLZs) if the zones are writable Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P2, 9.12.0 -> 9.12.3-P2, and versions 9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13 development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for vulnerability to CVE-2019-6465. 1679304: CVE-2019-6465 bind: Controls for zone transfers may not be properly applied to DLZs if the zones are writable CVE-2018-5745: 1679303: CVE-2018-5745 bind: An assertion failure if a trust anchor rolls over to an unsupported key algorithm when using managed-keys "managed-keys" is a feature which allows a BIND resolver to automatically maintain the keys used by trust anchors which operators configure for use in DNSSEC validation. Due to an error in the managed-keys feature it is possible for a BIND server which uses managed-keys to exit due to an assertion failure if, during key rollover, a trust anchor's keys are replaced with keys which use an unsupported algorithm. Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P1, 9.12.0 -> 9.12.3-P1, and versions 9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13 development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for vulnerability to CVE-2018-5745.
Fixed packages 17
| Release | Package | Fixed in |
|---|---|---|
| Amazon Linux · 2 | bind | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-chroot | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-debuginfo | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-devel | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-export-devel | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-export-libs | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-libs | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-libs-lite | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-license | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-lite-devel | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-pkcs11 | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-pkcs11-devel | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-pkcs11-libs | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-pkcs11-utils | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-sdb | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-sdb-chroot | 32:9.11.4-9.P2.amzn2.0.4 |
| Amazon Linux · 2 | bind-utils | 32:9.11.4-9.P2.amzn2.0.4 |
Vulnerabilities 3
-
High 7.5
TCP-pipelined queries can bypass tcp-clients limit
With pipelining enabled each incoming query on a TCP connection requires a similar resource allocation to a query received via UDP or via TCP without pipelining enabled. A client using a TCP-pipelined connection to a server could consume more resources than t…
-
Medium 5.3
Zone transfer controls for writable DLZ zones were not effective
Controls for zone transfers may not be properly applied to Dynamically Loadable Zones (DLZs) if the zones are writable Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P2, 9.12.0 -> 9.12.3-P2, and versions 9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported…
-
Medium 4.9
An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys
"managed-keys" is a feature which allows a BIND resolver to automatically maintain the keys used by trust anchors which operators configure for use in DNSSEC validation. Due to an error in the managed-keys feature it is possible for a BIND server which uses m…