Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning

To: <debian-security@lists.debian.org>
Subject: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning
From: John Elliot <johnelliot67@hotmail.com>
Date: Thu, 10 Jul 2008 18:12:58 +1030
Message-id: <BAY119-W6D0F11310DA85C8710B81DA910@phx.gbl>
In-reply-to: <20080710073851.A39F213A69D1@liszt.debian.org>
References: <20080710073848.32E2F13A69BE@liszt.debian.org> <20080710073851.A39F213A69D1@liszt.debian.org>

Hi,

We have a couple of Sarge servers running bind9(9.2.4-1sarge3) that appear to be vulnerable to the DNS cache poisoning issue(Looks like port randomization was only introduced in bind9.3?) - As the servers cannot be upgraded at this time to etch, what is the recommended course of action? Backports and upgrade to 9.3?

Try ninemsn dating now! Meet singles near you.

Reply to:

Follow-Ups:
- Re: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning
  - From: Vincent Deffontaines <vincent@gryzor.com>
- Re: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning
  - From: Florian Weimer <fw@deneb.enyo.de>

Prev by Date: Re: [SECURITY] [DSA 1605-1] DNS vulnerability impact on the libc stub resolver
Next by Date: Re: [SECURITY] [DSA 1605-1] DNS vulnerability impact on the libc stub resolver
Previous by thread: Re: [SECURITY] [DSA 1606-1] poppler packages fix execution of arbitrary code
Next by thread: Re: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning
Index(es):
- Date
- Thread