The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.
It was discovered that named did not invalidate previously cached SIG records when adding an NCACHE record for the same entry to the cache. A remote attacker allowed to send recursive DNS queries to named could use this flaw to crash named. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3613 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by RedHat:
|Product:||Affected Version(s):||Risk Level:||Actions:|
|Avaya Aura™ Communication Manager||4.x, 5.2, 5.2.1 without Security Service Pack 2||Low||Upgrade to Communication Manager 5.2.1 and install Security Service Pack 2 (PLAT-rhel4-1012).|
|Avaya Intuity AUDIX LX||2.0 including 2.0 SP1 and 2.0 SP2||Low||See recommended actions below. This advisory will not be addressed as no further releases are planned.|
|Avaya Message Networking||3.1, 5.2, 5.2.1, 5.2.2, 5.2.3||Low||Upgrade to MN 5.2.4 or later.|
|Avaya Messaging Storage Server||4.x, 5.0, 5.1.x, 5.2 thru 5.2.8||Low||Upgrade to MSS 5.2.9 or later.|
|Avaya Aura™ SIP Enablement Services||4.x, 5.x||Low||See recommended actions below. This advisory will not be addressed as no further releases are planned.|
|Avaya Proactive Contact||4.0 thru 4.2.1||Low||Upgrade to PC 4.2.2 or later.|
|Avaya Voice Portal||4.x||Low||Upgrade to VP 5.1.2 or later.|
Recommended Actions for System Products:
Avaya strongly recommends that customers follow networking and security best practices by implementing firewalls, ACLs, physical security or other appropriate access restrictions. Though Avaya believes such restrictions should always be in place; risk to Avaya's product and the surrounding network from this potential vulnerability may be mitigated by ensuring these practices are implemented until such time as a product update is available or the recommended action is applied. Further restrictions as deemed necessary based on the customer's security policies may be required during this interim period.
When determining risk, Avaya takes into account many factors as outlined by Avaya's Security Vulnerability Classification Policy. The following table describes factors that mitigate the risk of specific vulnerabilities for affected Avaya products:
||This vulnerability is rated a Low risk because bind is installed on the affected products, but is not exploitable because named is not installed.|
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.
|Avaya Aura™ Application Enablement Services 4.x/5.x||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the AES application.|
|CVLAN||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application.|
|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.|
|Avaya Aura™ Presence Services||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the PS application.|
|Avaya Aura™ System Manager 1.0||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the SMGR application.|
|Voice Portal||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the Voice Portal application.|
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends that customers follow recommended actions supplied by Red Hat regarding their Enterprise Linux.
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.
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.
V 1.0 - January 28, 2011 - Initial Statement issued.
V 2.0 - August 5, 2011 - Changed CM affected versions and actions.
V 3.0 - December 13, 2011 - Changed VP actions.
V 4.0 - December 20, 2011 - Changed MN affected versions and actions.
V 5.0 - March 7, 2012 - Changed MSS and PC affected versions and actions and advisory status to final.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or firstname.lastname@example.org.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2011 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.