Bug 1762958

Summary:	CVE-2019-6476 bind: An error in QNAME minimization code can cause BIND to exit with an assertion failure [fedora-all]
Product:	[Fedora] Fedora	Reporter:	kat <kbost>
Component:	bind	Assignee:	Petr Menšík <pemensik>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	30	CC:	anon.amish, mruprich, msehnout, pemensik, pzhukov, thoger, thozza, vonsch, zdohnal
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-21 09:40:11 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:	1762957

Description kat 2019-10-17 21:49:09 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-all.

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.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

Comment 1 kat 2019-10-17 21:49:11 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

# low, medium, high, urgent (required)
severity=medium

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1762957,1762958

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# 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 web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

Comment 2 Tomas Hoger 2019-10-20 21:18:16 UTC

AFAICS, Fedora (all currently released version and also rawhide) only had bind 9.11.x, while this issue only affected 9.14.x and 9.15.x.  Hence Fedora should be unaffected.

Comment 3 Petr Menšík 2019-10-21 09:40:11 UTC

I have work-in-progress branch with 9.14.x version [1], but it is not still ready to use. Rebased it to contain this issue fix. Once finished, latest version with proper fixes for these issues would be used. Until that time, 9.11.x is unaffected. ISC also corrected the announce a bit later, stating the same [2].

1. https://src.fedoraproject.org/fork/pemensik/rpms/bind/tree/v9_14
2. https://lists.isc.org/pipermail/bind-announce/2019-October/001139.html