These packages provide the OpenJDK 6 Java Runtime Environment and the OpenJDK 6 Software Development Kit.
defaultReadObject of the Serialization API could be tricked into setting a volatile field multiple times, which could allow a remote attacker to execute arbitrary code with the privileges of the user running the applet or application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3569 to this issue.
Race condition in the way objects were deserialized could allow an untrusted applet or application to misuse the privileges of the user running the applet or application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3568 to this issue.
Miscalculation in the OpenType font rendering implementation caused out-of-bounds memory access, which could allow remote attackers to execute code with the privileges of the user running the java process. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3567 to this issue.
JPEGImageWriter.writeImage in the imageio API improperly checked certain image metadata, which could allow a remote attacker to execute arbitrary code in the context of the user running the applet or application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3565 to this issue.
Double free in IndexColorModel could cause an untrusted applet or application to crash or, possibly, execute arbitrary code with the privileges of the user running the applet or application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3562 to this issue.
The privileged accept method of the ServerSocket class in the Common Object Request Broker Architecture (CORBA) implementation in OpenJDK allowed it to receive connections from any host, instead of just the host of the current connection. An attacker could use this flaw to bypass restrictions defined by network permissions. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3561 to this issue.
Flaws in the Swing library could allow an untrusted application to modify the behavior and state of certain JDK classes. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3557 to this issue.
Flaws in the CORBA implementation could allow an attacker to execute arbitrary code by misusing permissions granted to certain system objects. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3554 to this issue.
UIDefault.ProxyLazyValue had unsafe reflection usage, allowing untrusted callers to create objects via ProxyLazyValue values. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3553 to this issue.
HttpURLConnection improperly handled the "chunked" transfer encoding method, which could allow remote attackers to conduct HTTP response splitting attacks. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3549 to this issue.
HttpURLConnection improperly checked whether the calling code was granted the "allowHttpTrace" permission, allowing untrusted code to create HTTP TRACE requests. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3574 to this issue.
HttpURLConnection did not validate request headers set by applets, which could allow remote attackers to trigger actions otherwise restricted to HTTP clients. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2010-3541 and CVE-2010-3573 to these issues.
The Kerberos implementation improperly checked the sanity of AP-REQ requests, which could cause a denial of service condition in the receiving Java Virtual Machine. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3564 to this issue.
The RHSA-2010:0339 update mitigated a man-in-the-middle attack in the way the TLS/SSL (Transport Layer Security/Secure Sockets Layer) protocols handle session renegotiation by disabling renegotiation. This update implements the TLS Renegotiation Indication Extension as defined in RFC 5746, allowing secure renegotiation between updated clients and servers. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-3555 to this issue.
The NetworkInterface class improperly checked the network "connect" permissions for local network addresses, which could allow remote attackers to read local network addresses. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3551 to this issue.
Information leak flaw in the Java Naming and Directory Interface (JNDI) could allow a remote attacker to access information about otherwise-protected internal network names. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3548 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Aura™ Conferencing Standard Edition | 6.0 | 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™ System Platform | 1.1, 6.0 thru 6.0.3.5.3 | Low | Upgrade to SP6.0 Patch 6.0.3.6.3 or later. Rated a Low Risk since the jdk in Domain-0 is not a daemon and is used in a very limited fashion for a single application that is not accessible through the network interface. |
Recommended Actions for System Products:
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's
product and the surrounding network from this potential
vulnerability may be mitigated by ensuring these
practices are implemented until such time as a product
update is available or the recommended action is applied.
Further restrictions as deemed necessary based on the
customer's security policies may be required during this
interim period.
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 4.x/5.x | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the AES application. |
| CVLAN | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application. |
| Avaya Integrated Management Suite (IMS) | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the IMS application. |
| Avaya Aura™ Presence Services | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the PS application. |
| Avaya Aura™ System Manager 1.0 | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the SMGR application. |
| Voice Portal | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the Voice Portal application. |
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends that customers follow recommended actions supplied by RedHat Linux.
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.
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.
V 1.0 - October 29, 2010 - Initial Statement issued.
V 2.0 - April 16, 2012 - Updated SP actions.
V 3.0 - August 20, 2013 - Updated Conferencing actions and updated ASA 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.
© 2010 Avaya Inc. All Rights Reserved. All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.