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 RRSIG 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.
A flaw was found in the DNSSEC validation code in named. If named had multiple trust anchors configured for a zone, a response to a request for a record in that zone with a bad signature could cause named to crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3762 to this issue.
It was discovered that, in certain cases, named did not properly perform DNSSEC validation of an NS RRset for zones in the middle of a DNSKEY algorithm rollover. This flaw could cause the validator to incorrectly determine that the zone is insecure and not protected by DNSSEC. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3614 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Aura™ Communication Manager | 6.0.x | Low | Upgrade to CM 6.2 or later. |
| Avaya IQ | 5.0, 5.1 | Low | Upgrade to IQ 5.2 or later. |
| Avaya Aura™ Presence Services | 6.0, 6.1, 6.1.1 | Low | Upgrade to PS 6.1.2 or later. |
| Avaya Aura™ Session Manager | 1.1, 5.2, 6.0.x, 6.1, 6.1.1 | Low | Upgrade to SM 5.2.4 or later 5.2.x version, or upgrade to SM 6.1.2 or later. |
| Avaya Aura™ System Manager | 5.2, 6.0.x, 6.1.x | Low | Upgrade to SMGR 6.2 or later. |
| Avaya Aura™ System Platform | 1.1, 6.0, 6.0.1, 6.0.2 | Low | Upgrade to SP 6.0.3 or later. |
| Avaya Voice Portal | 5.0, 5.1, 5.1.1 | 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 the listed affected Avaya products:
| Vulnerability | Mitigating Factors |
|---|---|
|
CVE-2010-3613 CVE-2010-3614 CVE-2010-3762 |
CM, IQ, PS, SMGR, SP and VP are rated a low risk due to the bind service not running or configured by default.
Only the bind-libs and bind-utils packages are installed on these products. SM is rated a low risk due to the bind server listening only on the local server which doesn't allow remote queries. |
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.
| Product: | Actions: |
|---|---|
| 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 RedHat 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 12, 2011 - Initial Statement issued.
V 2.0 - December 15, 2011 - Changed affected IQ, SM, SP and VP affected versions and actions.
V 3.0 - April 5, 2012 - Changed CM, PS and SMGR 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 securityalerts@avaya.com.
© 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.