Oracle Solaris Critical Update (CVE-2012-3210 CVE-2012-0217 CVE-2012-3187 CVE-2012-3207 CVE-2012-3208 CVE-2012-3212 CVE-2012-3211 CVE-2012-3215)

Original Release Date: November 8, 2012
Last Revised: June 17, 2013
Number: ASA-2012-463
Risk Level: Medium
Advisory Version: 3.0
Advisory Status: Final

1. Overview:

New Solaris 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 - October 2012 and contains the following security issues.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: Kernel). The supported version that is affected is 11. Easily exploitable vulnerability allows successful unauthenticated network attacks via TCP/IP. 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-3210 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: Kernel). Supported versions that are affected are 10 and 11. Easily exploitable vulnerability requiring logon to Operating System. Successful attack of this vulnerability can result in unauthorized Operating System takeover including arbitrary code execution. Note: This issue only affects Solaris instances running on platforms other than SPARC. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0217 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: Kernel). The supported version that is affected is 10. Difficult to exploit vulnerability requiring logon to Operating System. Successful attack of this vulnerability can result in unauthorized Operating System takeover including arbitrary code execution. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3187 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: Kernel). Supported versions that are affected are 9, 10 and 11. Easily exploitable vulnerability requiring logon to Operating System. 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-3207 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: Kernel/RCTL). Supported versions that are affected are 10 and 11. Easily exploitable vulnerability requiring logon to Operating System. 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-3208 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: Kernel). Supported versions that are affected are 10 and 11. Difficult to exploit vulnerability requiring logon to Operating System. Successful attack of this vulnerability can result in unauthorized Operating System hang or frequently repeatable crash (complete DOS). Note: This issue only affects Solaris on SPARC T4 servers. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3212 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: Kernel/System Call). Supported versions that are affected are 10 and 11. Easily exploitable vulnerability requiring logon to Operating System plus additional login/authentication to component or subcomponent. Successful attack of this vulnerability can escalate attacker privileges resulting 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-3211 to this issue.

Vulnerability in the Solaris component of Oracle Sun Products Suite (subcomponent: Kernel). Supported versions that are affected are 10 and 11. Easily exploitable vulnerability requiring logon to Operating System plus additional login/authentication to component or subcomponent. Successful attack of this vulnerability can escalate attacker privileges resulting in unauthorized read access to a subset of Solaris accessible data. Note: This issue only affects Solaris on the SPARC platform. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3215 to this issue.

2. Avaya System Products using an affected 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 thru R16.3 load eg.e Medium Upgrade to R16.3 load eg.f or later as detailed in PCN1711Su
Avaya IR 4.0 Medium Upgrade to 4.0 Service Pack 6 and install Solaris 10 Patch Cluster (Oct 2012) for IR 4.0 Service Pack 6.

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-3210
There is no risk for CMS or IR as Solaris 11 is not used.
CVE-2012-0217
CVE-2012-3187
CVE-2012-3215
These are a medium risk for CMS and IR due to the potential for privilege escalation.
CVE-2012-3207
CVE-2012-3208
CVE-2012-3212
CVE-2012-3211
These are a medium risk for CMS and IR due to the potential for an authorized user to cause a Denial of Service.

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 - November 8, 2012 - Initial Statement issued.
V 1.1 - November 8, 2012 - Minor format changes to the overview section.
V 2.0 - February 20, 2013- Updated IR actions.
V 3.0 - June 17, 2013 - Updated CMS 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.

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