From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] bind: Update to 9.10.3
Date: Sat, 07 Nov 2015 13:30:22 +0000 [thread overview]
Message-ID: <1446903022.2587.0.camel@ipfire.org> (raw)
In-Reply-To: <1446878037-1121-1-git-send-email-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2705 bytes --]
Oh dear.
Most of these issues are in the server, which is not used in IPFire,
but I decided to pull this for Core Update 95.
-Michael
On Sat, 2015-11-07 at 07:33 +0100, Matthias Fischer wrote:
> bind: Update to 9.10.3
>
> Security fixes:
> An incorrect boundary check in the OPENPGPKEY rdatatype could trigger
> an assertion failure. This flaw is disclosed in CVE-2015-5986. [RT
> #40286]
>
> A buffer accounting error could trigger an assertion failure when
> parsing certain malformed DNSSEC keys.
> This flaw was discovered by Hanno Böck of the Fuzzing Project, and is
> disclosed in CVE-2015-5722. [RT #40212]
>
> A specially crafted query could trigger an assertion failure in
> message.c.
> This flaw was discovered by Jonathan Foote, and is disclosed in CVE
> -2015-5477. [RT #40046]
>
> On servers configured to perform DNSSEC validation, an assertion
> failure could be triggered on answers from a specially configured
> server.
> This flaw was discovered by Breno Silveira Soares, and is disclosed
> in CVE-2015-4620. [RT #39795]
>
> Bug fixes:
> Asynchronous zone loads were not handled correctly when the zone load
> was already in progress; this could trigger a crash in zt.c. [RT
> #37573]
>
> A race during shutdown or reconfiguration could cause an assertion
> failure in mem.c. [RT #38979]
>
> Some answer formatting options didn't work correctly with dig +short.
> [RT #39291]
>
> Malformed records of some types, including NSAP and UNSPEC, could
> trigger assertion failures when loading text zone files. [RT #40274]
> [RT #40285]
>
> Fixed a possible crash in ratelimiter.c caused by NOTIFY messages
> being removed from the wrong rate limiter queue. [RT #40350]
>
> The default rrset-order of random was inconsistently applied. [RT
> #40456]
>
> BADVERS responses from broken authoritative name servers were not
> handled correctly. [RT #40427]
>
> Several bugs have been fixed in the RPZ implementation.
>
> For a complete list, see:
> https://kb.isc.org/article/AA-01306/0/BIND-9.10.3-Release-Notes.html
>
> Regards,
> Matthias
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> lfs/bind | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/bind b/lfs/bind
> index 0814cde..6480798 100644
> --- a/lfs/bind
> +++ b/lfs/bind
> @@ -25,7 +25,7 @@
>
> include Config
>
> -VER = 9.10.2-P4
> +VER = 9.10.3
>
> THISAPP = bind-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -43,7 +43,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = 8b1f5064837756c938eadc1537dec5c7
> +$(DL_FILE)_MD5 = d8cbf04a62a139a841d4bf878087a555
>
> install : $(TARGET)
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-11-07 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 6:33 Matthias Fischer
2015-11-07 13:30 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1446903022.2587.0.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox