Security Vulnerability in BIND 8 May Allow Cache Poisoning Attack (Sun 103063)

Original Release Date: October 29, 2007
Last Revised: June 19, 2009
Number: ASA-2007-448
Risk Level: Low
Advisory Version: 2.0
Advisory Status: Final

1. Overview:

A new Sun Alert Notification from Sun Microsystems has been issued and is described below. Issues which have been resolved by Sun Microsystems have been indicated as such. Notifications without a resolution may have restrictions to additional information on the sunsolve.sun.com website.

103063
Security Vulnerability in BIND 8 May Allow Cache Poisoning Attack
Product: Solaris 9 Operating System, Solaris 8 Operating System
Category: Security
Date Released: 18-Sep-2007
http://sunsolve.sun.com/search/document.do?assetkey=1-26-103063-1

The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-2930 to this issue.

Avaya System Products using a Sun Microsystems Operating System:
Avaya system products include an Operating System with the product when it is delivered. Avaya Call Management System (CMS) and Avaya Interactive Response (IR) are both shipped with an operating system from Sun Microsystems. Actions to be taken on those products are described below.

Recommended Actions:
Follow the recommended actions for the products listed below. This advisory will be updated as additional information becomes available.

Product: Affected Version(s): Risk Level: Actions:
Avaya CMS R14.1 and ealier Low Although CMS does not support use as a DNS server, the underlying BIND packages do exist.

Upgrade to CMS R15 or later.
Avaya IR 2.0 on Solaris 8 Low Although IR does not support use as a DNS server, the underlying BIND packages do exist.

Install Solaris 8 Patch Cluster for Avaya IR 2.0 Service Pack 2.

2. Additional Information:

Additional information may also be available via the Avaya support website and through your Avaya account representative. Please contact your Avaya product support representative, or dial 1-800-242-2121, with any questions.

3. Disclaimer:

ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC., ON BEHALF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS "AVAYA"), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS' SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, INCIDENTAL, STATUTORY, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA.

4. Revision History:

V 1.0 - October 29, 2007 - Initial Statement issued.
V 2.0 - June 19, 2009 - Changed CMS and IR affected versions and actions and ASA status to final.

Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or securityalerts@avaya.com.

© 2007 Avaya Inc. All Rights Reserved. All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.