Skip to content
OpenAdvisories
High SUSE-SU-2017:1000-1 5 CVEs

Security update for bind

Published Apr 13, 2017 · Updated Feb 4, 2026

Summary

This update for bind fixes the following security issues:

CVE-2017-3137 (bsc#1033467):
Mistaken assumptions about the ordering of records in the answer
section of a response containing CNAME or DNAME resource records
could have been exploited to cause a denial of service of a bind
server performing recursion.

CVE-2017-3136 (bsc#1033466):
An attacker could have constructed a query that would cause a denial
of service of servers configured to use DNS64.

CVE-2017-3138 (bsc#1033468):
An attacker with access to the BIND control channel could have caused
the server to stop by triggering an assertion failure.

CVE-2016-6170 (bsc#987866):
Primary DNS servers could have caused a denial of service of secondary DNS servers via a large AXFR response.
IXFR servers could have caused a denial of service of IXFR clients via a large IXFR response.
Remote authenticated users could have caused a denial of service of primary DNS servers via a large UPDATE message.

CVE-2016-2775 (bsc#989528):
When lwresd or the named lwres option were enabled, bind allowed remote attackers to cause a denial of service
(daemon crash) via a long request that uses the lightweight resolver protocol.

Fixed packages 9

ReleasePackageFixed in
SUSE · Linux Enterprise Point of Sale 11 SP3 bind 9.9.6P1-0.44.1
SUSE · SLES 11 SP3 Linux Enterprise Server 11 SP3-LTSS bind 9.9.6P1-0.44.1
SUSE · SLES 11 SP3 Linux Enterprise Server 11 SP3-TERADATA bind 9.9.6P1-0.44.1
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 bind 9.9.6P1-0.44.1
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 bind 9.9.6P1-0.44.1
SUSE · SLES 11 SP4 Linux Enterprise Software Development Kit 11 SP4 bind 9.9.6P1-0.44.1
SUSE · Manager 2.1 bind 9.9.6P1-0.44.1
SUSE · Manager Proxy 2.1 bind 9.9.6P1-0.44.1
SUSE · OpenStack Cloud 5 bind 9.9.6P1-0.44.1

Vulnerabilities 5

  • High 7.5

    A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

    Mistaken assumptions about the ordering of records in the answer section of a response containing CNAME or DNAME resource records could lead to a situation in which named would exit with an assertion failure when processing a response in which records occurre…

  • Medium 6.5

    named exits with a REQUIRE assertion failure if it receives a null command string on its control channel

    named contains a feature which allows operators to issue commands to a running server by communicating with the server process over a control channel, using a utility program such as rndc. A regression introduced in a recent feature change has created a situa…

  • Medium 5.9
    CVE-2017-3136 EPSS 11%

    An error handling synthesized records could cause an assertion failure when using DNS64 with "break-dnssec yes;"

    A query with a specific set of characteristics could cause a server using DNS64 to encounter an assertion failure and terminate. An attacker could deliberately construct a query, enabling denial-of-service against a server if it was configured to use the DNS6…

  • Unscored —
    CVE-2016-2775 EPSS 63%

    ISC BIND 9.x before 9.9.9-P2, 9.10.x before 9.10.4-P2, and 9.11.x before 9.11.0b2, when lwresd or the named lwres optio…

  • Unscored —
    CVE-2016-6170 EPSS 41%

    ISC BIND through 9.9.9-P1, 9.10.x through 9.10.4-P1, and 9.11.x through 9.11.0b1 allows primary DNS servers to cause a …

References

  • report
    https://bugzilla.suse.com/1033466
  • report
    https://bugzilla.suse.com/1033467
  • report
    https://bugzilla.suse.com/1033468
  • report
    https://bugzilla.suse.com/987866
  • report
    https://bugzilla.suse.com/989528
  • web
    https://www.suse.com/security/cve/CVE-2016-2775
  • web
    https://www.suse.com/security/cve/CVE-2016-6170
  • web
    https://www.suse.com/security/cve/CVE-2017-3136
  • web
    https://www.suse.com/security/cve/CVE-2017-3137
  • web
    https://www.suse.com/security/cve/CVE-2017-3138