bind security update (RHSA-2007-0740)

Original Release Date: September 14, 2007
Last Revised: January 23, 2009
Number: ASA-2007-389
Risk Level: Low
Advisory Version: 4.0
Advisory Status: Interim

1. Overview:

Berkeley Internet Name Domain (BIND) provides tools and a server for the Domain Name System (DNS) protocols.

A vulnerability has been discovered in the way BIND generates IDs for outbound DNS queries. An attacker who was able to acquire a finite set of query IDs could predict future query IDs. This could allow the attacker to potentially poison a DNS cache, causing incorrect DNS data to be returned. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-2926 to this issue.

More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:

2. Avaya System Products with bind installed:

Product: Affected Version(s): Risk Level: Actions:
Avaya Communication Manager CM 2.x, 3.x, 4.x Low Upgrade to CM 5.0 or later to resolve this issue.
Avaya Intuity LX IALX 2.0 SP1 and earlier Low Upgrade to IALX 2.0 SP2 to resolve this issue.
Avaya EMMC EMMC 1.017, 1.021 Low This will not be addressed as no further release of EMMC are planned.
Avaya Messaging Storage Server 4.0 and earlier Low Upgrade to MSS 5.0 or later to resolve this issue.
Avaya Message Networking All Low See recommended actions below.  This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy
Avaya CCS/SES 4.0 and earlier Low Upgrade to SES 5.0 or later to resolve this issue
Avaya AES AES 3.1.3 and earlier

AES 4.0, 4.1
Low

Low
Upgrade to AES 3.1.4 or later to resolve this issue.

Upgrade to AES 4.2 or later to resolve this issue.

Recommended Actions:
For all system products which use vulnerable versions of bind, Avaya recommends that customers restrict local and network access to the server. This restriction should be enforced through the use of physical security, firewalls, ACLs, VPNs, and other generally-accepted networking practices until such time as an update becomes available and can be installed.

3. Avaya Software-Only Products:

Avaya software-only products operate on general-purpose operating systems. Occasionally vulnerabilities may be discovered in the underlying operating system or applications that come with the operating system. These vulnerabilities often do not impact the software-only product directly but may threaten the integrity of the underlying platform.

In the case of this advisory Avaya software-only products are not affected by the vulnerability directly but the underlying Linux platform may be. Customers should determine on which Linux operating system the product was installed and then follow that vendor's guidance.

4. Software-Only Products:

Product: Actions:
CVLAN Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application. The CVLAN application does not require the software described in this advisory.
Avaya Integrated Management Suite (IMS) Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the IMS application. The IMS application does not require the software described in this advisory.

Recommended Actions:
In the event that the affected package is installed, Avaya recommends that customers follow recommended actions supplied by RedHat Linux.

5. 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.

6. 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.

7. Revision History:

V 1.0 - September 14, 2007 - Initial Statement issued.
V 2.0 - January 8, 2008 - Updated resolution for a number of products.
V 3.0 - December 24, 2008 - Changed IALX recommended actions.
V 4.0 - January 23, 2009 - Changed MSS affected versions and recommended actions,changed EMMC recommended actions, and changed SES, AES affected versions.

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.