Bug 1291911

Summary:	CVE-2015-8461 bind: race condition when handling socket errors can lead to an assertion failure in resolver.c [fedora-23]
Product:	[Fedora] Fedora	Reporter:	Tomas Hoger <thoger>
Component:	bind	Assignee:	Tomáš Hozza <thozza>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	23	CC:	psimerda, thozza, vonsch
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	bind-9.10.3-7.P2.fc23 bind-9.10.3-7.P2.fc22	Doc Type:	Release Note
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-19 18:25:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1291186

Description Tomas Hoger 2015-12-15 21:08:35 UTC

This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

fedora-23 tracking bug for bind: see blocks bug list for full details of the security issue(s).

This bug is never intended to be made public, please put any public notes
in the blocked bugs.

[bug automatically created by: add-tracking-bugs]

Comment 1 Tomas Hoger 2015-12-15 21:08:41 UTC

Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1291186,1291911

# Description of your update
notes=Security fix for CVE-2015-8461

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi update submission link(s) instead:

https://bodhi.fedoraproject.org/updates/new?type_=security&bugs=1291186,1291911

Comment 2 Fedora Update System 2015-12-16 18:01:11 UTC

bind-9.10.3-4.P2.fc23 dnsperf-2.0.0.0-19.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-09bf9e06ea

Comment 3 Fedora Update System 2015-12-16 18:43:07 UTC

bind-9.10.3-7.P2.fc22 dnsperf-2.0.0.0-19.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-2df40de264

Comment 4 Fedora Update System 2015-12-17 10:27:49 UTC

bind-9.10.3-7.P2.fc22, dnsperf-2.0.0.0-19.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update dnsperf bind'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-2df40de264

Comment 5 Fedora Update System 2015-12-17 10:28:21 UTC

bind-9.10.3-7.P2.fc23, dnsperf-2.0.0.0-19.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update bind dnsperf'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-09bf9e06ea

Comment 6 Fedora Update System 2015-12-17 11:46:29 UTC

bind-9.10.3-7.P2.fc23 bind-dyndb-ldap-8.0-4.fc23 dnsperf-2.0.0.0-19.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-09bf9e06ea

Comment 7 Fedora Update System 2015-12-17 11:46:46 UTC

bind-9.10.3-7.P2.fc22 bind-dyndb-ldap-7.0-6.fc22 dnsperf-2.0.0.0-19.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-2df40de264

Comment 8 Fedora Update System 2015-12-18 11:27:36 UTC

bind-9.10.3-7.P2.fc22, bind-dyndb-ldap-7.0-6.fc22, dnsperf-2.0.0.0-19.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update bind-dyndb-ldap dnsperf bind'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-2df40de264

Comment 9 Fedora Update System 2015-12-18 11:56:22 UTC

bind-9.10.3-7.P2.fc23, bind-dyndb-ldap-8.0-4.fc23, dnsperf-2.0.0.0-19.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update bind-dyndb-ldap bind dnsperf'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-09bf9e06ea

Comment 10 Fedora Update System 2015-12-19 18:25:01 UTC

bind-9.10.3-7.P2.fc23, bind-dyndb-ldap-8.0-4.fc23, dnsperf-2.0.0.0-19.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2015-12-22 07:22:47 UTC

bind-9.10.3-7.P2.fc22, bind-dyndb-ldap-7.0-6.fc22, dnsperf-2.0.0.0-19.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.