Ethernet Driver Vulnerability (CVE-2010-4433)

Original Release Date: February 2, 2011
Last Revised: March 16, 2012
Number: ASA-2011-015
Risk Level: Low
Advisory Version: 2.0
Advisory Status: Final

1. Overview:

New Critical Patch Updates or Security Alerts have been issued by Oracle. Specific updates or alerts pertaining to this advisory are described below. Additional information about this issue may be found on the Oracle Critical Patch Updates and Security Alerts website. Content outlined in this Avaya Security Advisory may also be found in the original advisory from Oracle.

CVE-2010-4433
Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: Driver). The supported version that is affected is 10. Easily exploitable vulnerability allows successful unauthenticated network attacks via Ethernet. Successful attack of this vulnerability can result in unauthorized read access to a subset of Solaris accessible data.
Component: Solaris
Subcomponent: Driver

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

2. Avaya System Products using a Solaris Operating System:

Some Avaya system products are delivered with a Solaris Operating System. Actions to be taken on these products are described below.

Product: Affected Version(s): Risk Level: Actions:
Avaya CMS R15, R16/R16.1/R16.2 Low Customers running R15 upgrade to R15ab.m or R15auxab.m or later.
Customers running R16/R6.1 upgrade to R16.2 and install patch 146018-02.
Customers running R16.2 install patch 146018-02.
Avaya IR 3.0, 4.0 Low Upgrade to IR 4.0 Service Pack 6 and install "Solaris 10 Patch Cluster (Jan 2012) for Avaya IR 4.0 Service Pack 6" or later.

Recommended Actions:
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.

Mitigating Factors:

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:

Vulnerability Mitigating Factors
CVE-2010-4433
This is a Low for CMS and IR as no critical system applications or processes would be affected.

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

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

5. Revision History:

V 1.0 - February 2, 2011 - Initial Statement issued.
V 2.0 - March 16, 2012 - Changed CMS and IR 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 identifying Avaya products by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.