Alerts This Week
Warning Icon 1 727
Alerts This Week
Warning Icon 1 727

Gentoo: 2017-01-26 Critical Update for BIND Denial of Service Issue

gentoo
Calendar Grey January 11, 2017
Dist Gentoo Esm H88
Gentoo GLSA 202401-15 covers a critical vulnerability in OpenSSH that may lead to service disruptions. Updating is advised for maintaining security.
A vulnerability in BIND might allow remote attackers to cause a Denial of Service condition.

Summary

A defect in BIND's handling of responses containing a DNAME answer can cause a resolver to exit after encountering an assertion failure in db.c or resolver.c.

Resolution

All BIND users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=net-dns/bind-9.10.4_p4"

References

[ 1 ] CVE-2016-8864 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8864

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201701-26
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
critical
Lowest
Low
Medium
High
Critical

Severity: Normal
Title: BIND: Denial of Service
Date: January 11, 2017
Bugs: #598750
ID: 201701-26

Synopsis

A vulnerability in BIND might allow remote attackers to cause a Denial of Service condition.

Background

BIND (Berkeley Internet Name Domain) is a Name Server.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-dns/bind < 9.10.4_p4 >= 9.10.4_p4

Impact

===== A remote attacker could send a specially crafted DNS request to the BIND resolver possibly resulting in a Denial of Service condition.

Workaround

There is no known workaround at this time.

Your message here