Oracle Solaris Critical Update (CVE-2012-3120 CVE-2008-4609 CVE-2012-3125 CVE-2001-0323 CVE-2011-2699)

Original Release Date: July 27, 2012
Last Revised: August 26, 2015
Number: ASA-2012-320
Risk Level: Medium
Advisory Version: 3.0
Advisory Status: Final

1. Overview:

New Critical Patch Updates or Security Alerts have been issued by Oracle on Oracle's Critical Patch Updates and Security Alerts website. Specific updates or alerts pertaining to this advisory are described below. The Oracle Advisory covering content outlined in this Avaya Security Advisory may be found in Oracle's Critical Patch Update Advisory - July 2012 and contains the following security issues.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: TCP/IP). The supported version that is affected is 8. Easily exploitable vulnerability allows successful unauthenticated network attacks via TCP. Successful attack of this vulnerability can result in unauthorized Operating System hang or frequently repeatable crash (complete DOS). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3120 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: TCP/IP). Supported versions that are affected are 8, 9 and 10. Difficult to exploit vulnerability allows successful unauthenticated network attacks via TCP. Successful attack of this vulnerability can result in unauthorized Operating System hang or frequently repeatable crash (complete DOS). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-4609 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: TCP/IP). Supported versions that are affected are 8, 9 and 10. Difficult to exploit vulnerability allows successful unauthenticated network attacks via TCP. Successful attack of this vulnerability can result in unauthorized Operating System hang or frequently repeatable crash (complete DOS). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3125 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: TCP/IP). Supported versions that are affected are 8, 9 and 10. Easily exploitable vulnerability allows successful unauthenticated network attacks via TCP/IP. Successful attack of this vulnerability can result in unauthorized update, insert or delete access to some Solaris accessible data and ability to cause a partial denial of service (partial DOS) of Solaris. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2001-0323 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: TCP/IP). Supported versions that are affected are 8, 9 and 10. Easily exploitable vulnerability allows successful unauthenticated network attacks via IPv6. Successful attack of this vulnerability can result in unauthorized update, insert or delete access to some Solaris accessible data. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2699 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.0.x, R16.0.x, R16.1.x, R16.2.x, R16.3 with a Patch bundle earlier than R16.3eg.3 Medium For R15, upgrade to R15ab.m/R15auxab.m or later and for R16.x, upgrade to R16.3eg.3 release or later to fix the vulnerabilities described in CVE-2008-4609, CVE-2012-3125 and CVE-2001-0323.
Avaya IR 4.0.x Low See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned. It is recommended that customers migrate to Avaya Experience Portal. Please contact your Avaya representative for information on the migration and ordering process.

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 products and the surrounding network from this potential vulnerability may be mitigated by ensuring these practices are implemented until such time as an Avaya provided product update or the recommended Avaya action is applied. Further restrictions as deemed necessary based on the customer's security policies may be required during this interim period, but customers should not modify the System Product operating system or application unless the change is approved by Avaya. Making changes that are not approved may void the Avaya product service contract.

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-2012-3120
The risk is rated None because Solaris 8 is not supported by either CMS or IR.
CVE-2008-4609
CVE-2012-3125
CVE-2001-0323
These vulnerabilities are fixed for CMS in the latest R15, R16 releases.
The risk is rated Medium for IR because connections are allowed only from trusted hosts and firewall rate limits mitigates the Denial of Service.
CVE-2011-2699
The risk is rated None for IR because it does not support IPv6.
The risk is rated Low for CMS because IPv6 is not enabled by default.

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 - July 27, 2012 - Initial Statement issued.
V 2.0 - September 6, 2012 - Modified risk rating, actions and mitigating factors based on CMS and IR inputs.
V 3.0 - August 26, 2015 - Updated actions for IR, and set 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 [email protected].

© 2012 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.