java-1.7.0-openjdk security update (RHSA-2013-1451)

Original Release Date: November 5, 2013
Last Revised: November 17, 2014
Number: ASA-2013-478
Risk Level: Medium
Advisory Version: 2.0
Advisory Status: Final

1. Overview:

The java-1.7.0-openjdk packages provide the OpenJDK 7 Java Runtime Environment and the OpenJDK 7 Java Software Development Kit.

Multiple input checking flaws were found in the 2D component native image parsing code. A specially crafted image file could trigger a Java Virtual Machine memory corruption and, possibly, lead to arbitrary code execution with the privileges of the user running the Java Virtual Machine. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-5782 to this issue.

The class loader did not properly check the package access for non-public proxy classes. A remote attacker could possibly use this flaw to execute arbitrary code with the privileges of the user running the Java Virtual Machine. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-5830 to this issue.

Multiple improper permission check issues were discovered in the 2D, CORBA, JNDI, and Libraries 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-5829, CVE-2013-5814, CVE-2013-5817, CVE-2013-5842, CVE-2013-5850 and CVE-2013-5838 to these issues.

Multiple input checking flaws were discovered in the JPEG image reading and writing code in the 2D component. An untrusted Java application or applet could use these flaws to corrupt the Java Virtual Machine memory and bypass Java sandbox restrictions. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-5809 to this issue.

The FEATURE_SECURE_PROCESSING setting was not properly honored by the javax.xml.transform package transformers. A remote attacker could use this flaw to supply a crafted XML that would be processed without the intended security restrictions. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-5802 to this issue.

Multiple errors were discovered in the way the JAXP and Security components processes XML inputs. A remote attacker could create a crafted XML that would cause a Java application to use an excessive amount of CPU and memory when processed. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-5825, CVE-2013-4002 and CVE-2013-5823 to these issues.

Multiple improper permission check issues were discovered in the Libraries, Swing, JAX-WS, JAXP, JGSS, AWT, Beans, and Scripting components in OpenJDK. An untrusted Java application or applet could use these flaws to bypass certain Java sandbox restrictions. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-3829, CVE-2013-5840, CVE-2013-5774, CVE-2013-5783, CVE-2013-5820, CVE-2013-5851, CVE-2013-5800, CVE-2013-5849, CVE-2013-5790 and CVE-2013-5784 to these issues.

It was discovered that the 2D component image library did not properly check bounds when performing image conversions. An untrusted Java application or applet could use this flaw to disclose portions of the Java Virtual Machine memory. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-5778 to this issue.

Multiple input sanitization flaws were discovered in javadoc. When javadoc documentation was generated from an untrusted Java source code and hosted on a domain not controlled by the code author, these issues could make it easier to perform cross-site scripting attacks. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-5804 and CVE-2013-5797 to these issues.

Various OpenJDK classes that represent cryptographic keys could leak private key information by including sensitive data in strings returned by toString() methods. These flaws could possibly lead to an unexpected exposure of sensitive key data. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-5780 to this issue.

The Java Heap Analysis Tool (jhat) failed to properly escape all data added into the HTML pages it generated. Crafted content in the memory of a Java program analyzed using jhat could possibly be used to conduct cross-site scripting attacks. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-5772 to this issue.

The Kerberos implementation in OpenJDK did not properly parse KDC responses. A malformed packet could cause a Java application using JGSS to exit. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-5803 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 RHEL6 with affected packages installed:

Product: Affected Version(s): Risk Level: Actions:
Avaya IP Office Server Edition 9.0 including SP1 and SP2 Medium Upgrade to 9.0 SP3 or later.
Avaya IP Office Application Server 9.0 including SP1 and SP2 Medium Upgrade to 9.0 SP3 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-3829
CVE-2013-5774
CVE-2013-5778
CVE-2013-5783
CVE-2013-5784
CVE-2013-5790
CVE-2013-5800
CVE-2013-5809
CVE-2013-5814
CVE-2013-5817
CVE-2013-5820
CVE-2013-5829
CVE-2013-5838
CVE-2013-5840
CVE-2013-5842
CVE-2013-5849
CVE-2013-5850
CVE-2013-5851
These are a Low risk because untrusted Java applications and applets are not allowed to run.
CVE-2013-5782 This is a Low risk because image parsing is non-standard functionality.
CVE-2013-5830 This is a Low risk because loading remotely supplied packages is not allowed.
CVE-2013-4002
CVE-2013-5802
CVE-2013-5823
CVE-2013-5825
These are a Medium risk because XML data processing can only be done by an authenticated user or from a trusted host.
CVE-2013-5797
CVE-2013-5804
These are a Low risk because javadoc generation is non-standard functionality.
CVE-2013-5780 This is a Medium risk as an authenticated user may access unauthorized sensitive key data.
CVE-2013-5772 This is a Low risk because the Java Heap Analysis Tool usage is non-standard functionality.
CVE-2013-5803 This is a Low risk because Kerberos is not used.

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 - November 5, 2013 - Initial Statement issued.
V 2.0 - November 17, 2014 - Changed IP Office SE and IP Office AS affected versions and 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.

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.