Solution: Currently, only RedHat has issued an update but other vendors should follow shortly.
The best temporary solution is to disable recursion on your name servers. This can be done by doing the following:
For BIND 8 change / add to named.conf:
options {
recursion no;
};
For BIND 4 change / add to named.boot
options no-recursion
Also ANY DNS server ought to run in a chroot'ed jail. This will in most cases limit the impact of a compromise.
BIND 9 is NOT vulnerable. BIND 9 may be an easy option for users of BIND 8 and an upgrade from BIND 4 isn't too difficult either. ISC recommends that you deploy BIND version 9.2.1, see more: http://www.isc.org/products/BIND/bind-security.html
EVEN IF YOU UPGRADE TO BIND 9.2.1, YOU SHOULD STILL DEPLOY A VENDOR UPDATE AS SOME RESOLVER LIBRARIES MAY NOT BE UPDATED.
Secunia will issue advisories regarding each individual system as more detailed information becomes available.
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
If you have new information regarding this Secunia advisory or a product in our database, please send it to us using either our web form or email us at vuln@secunia.com.
Ideas, suggestions, and other feedback are most welcome.