Oracle Java Critical Update Combined CVEs (February 2012)

Original Release Date: March 27, 2012
Last Revised: September 29, 2015
Number: ASA-2012-128
Risk Level: Low
Advisory Version: 3.0
Advisory Status: Final

1. Overview:

New Critical Java Security Updates 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 - February 2012 and contains the following security issues.

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, and 6 Update 30 and earlier, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0497 to this issue.

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Update 30 and earlier, and 5.0 Update 33 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0498 to this issue.

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Update 30 and earlier, 5.0 Update 33 and earlier, and 1.4.2_35 and earlier; and JavaFX 2.0.2 and earlier; allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0499 to this issue.

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Update 30 and earlier, and JavaFX 2.0.2 and earlier allows remote untrusted Java Web Start applications and untrusted Java applets to affect confidentiality, integrity, and availability via unknown vectors related to Deployment. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0500 to this issue.

Unspecified vulnerability in the JavaFX component in Oracle Java SE JavaFX, 1.3.0 and earlier, and 1.2.2 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0508 to this issue.

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, and 6 Update 30 and earlier, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Install and the Java Update mechanism. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0504 to this issue.

Unspecified vulnerability in the Virtual Desktop Infrastructure (VDI) component in Oracle Virtualization 3.2 allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Session. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3571 to this issue.

Timezone vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Update 30 and earlier, 5.0 Update 33 and earlier, and 1.4.2_35 and earlier allows remote untrusted Java Web Start applications and untrusted Java applets to affect confidentiality, integrity, and availability, related to setting a default timezone value.The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0503 to this issue.

Leaked references to Serialization Exceptions vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Update 30 and earlier, 5 Update 33 and earlier, and 1.4.2_35 and earlier allows remote untrusted Java Web Start applications and untrusted Java applets to affect confidentiality, integrity, and availability via unknown vectors related to Serialization. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0505 to this issue.

A flaw in the AWTKeyboardFocus class in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Update 30 and earlier, 5.0 Update 33 and earlier, and 1.4.2_35 and earlier allows remote untrusted Java Web Start applications and untrusted Java applets to affect confidentiality and availability, related to AWT. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0502 to this issue.

Remote Stack Overflow in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Update 30 and earlier, 5.0 Update 33 and earlier, and 1.4.2_35 and earlier allows remote attackers to affect confidentiality and availability via unknown vectors related to Sound. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3563 to this issue.

Oracle Glassfish 2.1.1, 3.0.1, and 3.1.1, as used in Communications Server 2.0, Sun Java System Application Server 8.1 and 8.2, and possibly other products, computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters, aka Oracle security ticket S0104869. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-5035 to this issue.

Remote Stack Overflow vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Update 30 and earlier, and 5.0 Update 33 and earlier allows remote attackers to affect availability via a crafted ZIP File. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0501 to this issue.

Improper protection of repository identifiers on certain CORBA objects in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Update 30 and earlier, 5.0 Update 33 and earlier, and 1.4.2_35 and earlier allows remote untrusted Java Web Start applications and untrusted Java applets to affect integrity via unknown vectors related to CORBA. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0506 to this issue.

2. Avaya System Products using affected versions of Java:

Some Avaya system products are delivered with the Java Standard Edition (SE) platform. Actions to be taken on these products are described below.

Product: Affected Version(s): Risk Level: Actions:
Avaya Aura® Application Enablement Services 5.2 thru 6.1.2 Low Upgrade to 6.1.3 or later.
Avaya Aura® Application Server 5300:
  • SIP Core
2.x, 3.x including PB1 thru PB4 Low Upgrade to 3.0 PB5 or later.
Avaya CMS R15.x, R16.x Low Contact Avaya support for the necessary package updates to resolve this issue.
Avaya Aura® Communication Manager 5.x Low Upgrade to 6.0 or later.
Avaya Aura® Conferencing Standard Edition 6.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 one of Avaya's conferencing solutions including Aura® Conferencing 8.0 or later.
Avaya Aura® Experience Portal 6.0 thru 6.0.1 Low Upgrade to 6.0.2 and Avaya Enterprise Linux for 6.0.2 or later.
Avaya IP Office Application Server 8.x and earlier Low Upgrade to 9.0 or later.
Avaya IQ 5.2 thru 5.2.5 Low Upgrade to 5.2.6 and install Patch 2 or later.
Avaya IR 4.0 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.
Avaya Meeting Exchange 5.0 thru 5.2 SP2 Low Upgrade to 5.2 SP3 or later.
Avaya Message Networking 5.2 including 5.2 SP14 Low Upgrade to 5.2 SP15 or later.
Avaya Aura® Messaging 6.0.x, 6.1 thru 6.2 Low Upgrade to 6.3 or later.
Avaya Messaging Application Server 5.2.x without SP16 Low Upgrade to 5.2 SP16 or later.
Avaya Message Storage Server 5.2.x without SP16 Low Upgrade to 5.2 SP16 or later.
Avaya Aura® Presence Services 6.0, 6.1 Low Upgrade to 6.2 or later.
Avaya Proactive Contact 4.2.x, 5.0.x Low Upgrade to 5.1 or later.
Avaya Aura® Session Manager 1.1, 5.2.x, 6.0 thru 6.3 Low Upgrade to 6.3.1 or later.
Avaya Aura® SIP Enablement Services 5.2.x and earlier Low See recommended actions below. This advisory will not be addressed as no further releases are planned.
Avaya Aura® System Manager 6.2 and earlier Low Upgrade to 6.3 or later.
Avaya Aura® System Platform 1.1, 6.0 thru 6.2 Low Upgrade to 6.3 or later.
Avaya Aura® Communication Manager Utility Services 6.1, 6.2 Low Upgrade to 6.3 or later.
Avaya Voice Portal 5.0.x, 5.1.x Low See recommended actions and Mitigating Factors table below. This advisory will not be addressed as there will be no further releases. It is recommended to upgrade to Avaya Aura® Experience Portal.

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-0497
CVE-2012-0498
CVE-2012-0499
These are a low risk for all products because 2D sub-component objects or graphics is not used.
CVE-2012-0500
CVE-2012-0502
CVE-2012-0503
CVE-2012-0505
CVE-2012-0506
These are a low risk for all products because untrusted Java Web Start applications and Java applets are not allowed to run on these systems.
CVE-2011-3563
This is a low risk for all products because they do not utilize the Sound component.
CVE-2012-0501
This is a low risk for products that allow processing of ZIP files because they can be downloaded only from trusted sources and modifying those sources requires administrative privileges.
CVE-2012-0504
This is a low risk for all products because installation and updates to the Java Run Time environment on Avaya System is not supported and would constitute non-standard user interaction by an administrative user.
CVE-2012-0508
This is a low risk for all products because the JavaFX component is not used.
CVE-2011-3571
CVE-2011-5035
There is no risk to any Avaya products because Oracle Virtualization and Oracle GlassFish are not installed.

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 - March 27, 2012 - Initial Statement issued.
V 2.0 - September 9, 2015 - Updated AES, AS5300, EP, IQ, MX, PS, SMGR, SM, SP, Message Networking affected versions and actions, and CMS, CM, CSE, IPOAS, Messaging, MAS, MSS, Proactive Contact, IR, SES, VP actions.
V 3.0 - September 29, 2015 - Updated US actions, 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 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.