java-1.6.0-openjdk security update (RHSA-2013-1014)

Original Release Date: July 22, 2013
Last Revised: August 4, 2016
Number: ASA-2013-352
Risk Level: Medium
Advisory Version: 5.0
Advisory Status: Final

1. Overview:

These packages provide the OpenJDK 6 Java Runtime Environment and the OpenJDK 6 Software Development Kit.

Multiple flaws were discovered in the ImagingLib and the image attribute, channel, layout and raster processing in the 2D component. An untrusted Java application or applet could possibly use these flaws to trigger Java Virtual Machine memory corruption. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-2470, CVE-2013-2471, CVE-2013-2472, CVE-2013-2473, CVE-2013-2463, CVE-2013-2465 and CVE-2013-2469 to these issues.

Integer overflow flaws were found in the way AWT processed certain input. An attacker could use these flaws to execute arbitrary code with the privileges of the user running an untrusted Java applet or application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-2459 to this issue.

Multiple improper permission check issues were discovered in the Sound and JMX components in OpenJDK. An untrusted Java application or applet could use these flaws to bypass Java sandbox restrictions. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-2448, CVE-2013-2457 and CVE-2013-2453 to these issues.

Multiple flaws in the Serialization, Networking, Libraries and CORBA components can be exploited by an untrusted Java application or applet to gain access to potentially sensitive information. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-2456, CVE-2013-2447, CVE-2013-2455, CVE-2013-2452, CVE-2013-2443 and CVE-2013-2446 to these issues.

It was discovered that the Hotspot component did not properly handle out-of-memory errors. An untrusted Java application or applet could possibly use these flaws to terminate the Java Virtual Machine. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-2445 to this issue.

It was discovered that the AWT component did not properly manage certain resources and that the ObjectStreamClass of the Serialization component did not properly handle circular references. An untrusted Java application or applet could possibly use these flaws to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-2444 and CVE-2013-2450 to these issues.

It was discovered that the Libraries component contained certain errors related to XML security and the class loader. A remote attacker could possibly exploit these flaws to bypass intended security mechanisms or disclose potentially sensitive information and cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-2407 and CVE-2013-2461 to these issues.

It was discovered that JConsole did not properly inform the user when establishing an SSL connection failed. An attacker could exploit this flaw to gain access to potentially sensitive information. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-2412 to this issue.

It was found that documentation generated by Javadoc was vulnerable to a frame injection attack. If such documentation was accessible over a network, and a remote attacker could trick a user into visiting a specially-crafted URL, it would lead to arbitrary web content being displayed next to the documentation. This could be used to perform a phishing attack by providing frame content that spoofed a login form on the site hosting the vulnerable documentation. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1571 to this issue.

It was discovered that the 2D component created shared memory segments with insecure permissions. A local attacker could use this flaw to read or write to the shared memory segment. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1500 to this issue.

More information about these vulnerabilities can be found in the security advisory issued by Red Hat:

2. Avaya System Products using a modified version of RHEL5 or RHEL6 with affected packages installed:

Product: Affected Version(s): Risk Level: Actions:
Avaya CMS R17.x Medium Contact Avaya support for the necessary package updates to resolve this issue.
Avaya Aura® Conferencing Standard Edition 6.x Medium 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 7.0 or later.
Avaya Aura® Experience Portal 6.x Low Upgrade to 7.0 and Avaya Enterprise Linux for 7.0 or later.
Avaya Meeting Exchange 6.2 thru 6.2 SP2 Medium Upgrade to 6.2 SP3 or later.
Avaya one-X® Client Enablement Services 6.2 Medium Upgrade to 6.2 SP1 or later.
Avaya Aura® System Platform 1.x thru 6.3 Medium Upgrade to 6.3.1 or later.
Avaya Aura® Communication Manager Utility Services 6.0, 6.1, 6.2 thru 6.2.8.0.15, 6.3 thru 6.3.1.0.20 Medium For 6.0 and 6.1, upgrade to 6.2 or 6.3 and follow action for appropriate upgraded version.
For 6.2, install Service Pack 6.2.9.0.15 or later.
For 6.3, install Service Pack 6.3.2.0.20 or later.

Recommended Actions for System Products:
Avaya strongly recommends following the 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 the System Product operating system or application should not be modified 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-2013-1500 This is a Low risk for all products because the 2D component is not used by default.
CVE-2013-1571 This is a Low risk for all products because Web browsing is considered non-standard user interaction.
CVE-2013-2407
CVE-2013-2461
These are a Low risk for Experience Portal because java-1.6.0-openjdk is not used by default.
These are a Medium risk for all other products because of the potential to obtain sensitive information or cause a denial of service.
CVE-2013-2412 This is a Low risk for Experience Portal because java-1.6.0-openjdk is not used by default.
This is a Low risk for all other products because of the potential to obtain non-critical sensitive information.
CVE-2013-2443
CVE-2013-2444
CVE-2013-2445
CVE-2013-2446
CVE-2013-2447
CVE-2013-2448
CVE-2013-2450
CVE-2013-2452
CVE-2013-2453
CVE-2013-2455
CVE-2013-2456
CVE-2013-2457
CVE-2013-2459
CVE-2013-2463
CVE-2013-2465
CVE-2013-2469
CVE-2013-2470
CVE-2013-2471
CVE-2013-2472
CVE-2013-2473
These are a low risk for all products because untrusted Java application and applets are not executed by default.

3. Avaya Software-Only Products:

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 Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the AES application.
CVLAN Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the CVLAN application.
Avaya Aura® Experience Portal Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the EP application.
Avaya Integrated Management Suite (IMS) Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the IMS application.
Avaya Aura® Presence Services Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the PS application.
Avaya Secure Access Link Gateway Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the SAL Gateway application.
Avaya Voice Portal Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the VP application.

Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends following the recommended actions supplied by Red Hat regarding their Enterprise Linux.

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

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

6. Revision History:

V 1.0 - July 22, 2013 - Initial Statement issued.
V 2.0 - January 10, 2014 - Changed EP actions and SP affected versions and actions.
V 3.0 - February 10, 2014 - Changed CMS and CMUS actions.
V 4.0 - August 5, 2014 - Changed one-X CES affected versions and actions.
V 5.0 - August 4, 2016 - Changed MX 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.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

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