RHSA-2011:1380: Red Hat Security Advisory: java-1.6.0-openjdk security update

Published Oct 18, 2011
·
Updated

These packages provide the OpenJDK 6 Java Runtime Environment and theOpenJDK 6 Software Development Kit.A flaw was found in the Java RMI (Remote Method Invocation) registryimplementation. A remote RMI client could use this flaw to executearbitrary code on the RMI server running the registry. (CVE-2011-3556)A flaw was found in the Java RMI registry implementation. A remote RMIclient could use this flaw to execute code on the RMI server withunrestricted privileges. (CVE-2011-3557)A flaw was found in the IIOP (Internet Inter-Orb Protocol) deserializationcode. An untrusted Java application or applet running in a sandbox coulduse this flaw to bypass sandbox restrictions by deserializingspecially-crafted input. (CVE-2011-3521)It was found that the Java ScriptingEngine did not properly restrict theprivileges of sandboxed applications. An untrusted Java application orapplet running in a sandbox could use this flaw to bypass sandboxrestrictions. (CVE-2011-3544)A flaw was found in the AWTKeyStroke implementation. An untrusted Javaapplication or applet running in a sandbox could use this flaw to bypasssandbox restrictions. (CVE-2011-3548)An integer overflow flaw, leading to a heap-based buffer overflow, wasfound in the Java2D code used to perform transformations of graphic shapesand images. An untrusted Java application or applet running in a sandboxcould use this flaw to bypass sandbox restrictions. (CVE-2011-3551)An insufficient error checking flaw was found in the unpacker for JAR filesin pack200 format. A specially-crafted JAR file could use this flaw tocrash the Java Virtual Machine (JVM) or, possibly, execute arbitrary codewith JVM privileges. (CVE-2011-3554)It was found that HttpsURLConnection did not perform SecurityManager checksin the setSSLSocketFactory method. An untrusted Java application or appletrunning in a sandbox could use this flaw to bypass connection restrictionsdefined in the policy. (CVE-2011-3560)A flaw was found in the way the SSL 3 and TLS 1.0 protocols used blockciphers in cipher-block chaining (CBC) mode. An attacker able to perform achosen plain text attack against a connection mixing trusted and untrusteddata could use this flaw to recover portions of the trusted data sent overthe connection. (CVE-2011-3389)Note: This update mitigates the CVE-2011-3389 issue by splitting the firstapplication data record byte to a separate SSL/TLS protocol record. Thismitigation may cause compatibility issues with some SSL/TLS implementationsand can be disabled using the jsse.enableCBCProtection boolean property.This can be done on the command line by appending the flag"-Djsse.enableCBCProtection=false" to the java command.An information leak flaw was found in the InputStream.skip implementation.An untrusted Java application or applet could possibly use this flaw toobtain bytes skipped by other threads. (CVE-2011-3547)A flaw was found in the Java HotSpot virtual machine. An untrusted Javaapplication or applet could use this flaw to disclose portions of the VMmemory, or cause it to crash. (CVE-2011-3558)The Java API for XML Web Services (JAX-WS) implementation in OpenJDK wasconfigured to include the stack trace in error messages sent to clients. Aremote client could possibly use this flaw to obtain sensitive information.(CVE-2011-3553)It was found that Java applications running with SecurityManagerrestrictions were allowed to use too many UDP sockets by default. Ifmultiple instances of a malicious application were started at the sametime, they could exhaust all available UDP sockets on the system.(CVE-2011-3552)This erratum also upgrades the OpenJDK package to IcedTea6 1.9.10. Refer tothe NEWS file, linked to in the References, for further information.All users of java-1.6.0-openjdk are advised to upgrade to these updatedpackages, which resolve these issues. All running instances of OpenJDK Javamust be restarted for the update to take effect.

Affected Software

40 affected componentsFixes available
redhat/java-1.6.0-openjdk<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk-debuginfo<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk-demo<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk-devel<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk-javadoc<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk-src<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk-debuginfo<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk-demo<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk-devel<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk-javadoc<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk-src<1:1.6.0.0-1.23.1.9.10.el5_7
1:1.6.0.0-1.23.1.9.10.el5_7
redhat/java-1.6.0-openjdk<1:1.6.0.0-1.40.1.9.10.el6_1
1:1.6.0.0-1.40.1.9.10.el6_1
redhat/java-1.6.0-openjdk-debuginfo<1:1.6.0.0-1.40.1.9.10.el6_1
1:1.6.0.0-1.40.1.9.10.el6_1
redhat/java-1.6.0-openjdk-devel<1:1.6.0.0-1.40.1.9.10.el6_1
1:1.6.0.0-1.40.1.9.10.el6_1
redhat/java-1.6.0-openjdk-javadoc<1:1.6.0.0-1.40.1.9.10.el6_1
1:1.6.0.0-1.40.1.9.10.el6_1
redhat/java-1.6.0-openjdk-demo<1:1.6.0.0-1.40.1.9.10.el6_1
1:1.6.0.0-1.40.1.9.10.el6_1
redhat/java-1.6.0-openjdk-src<1:1.6.0.0-1.40.1.9.10.el6_1
1:1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-debuginfo-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-debuginfo-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-demo-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-demo-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-devel-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-devel-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-javadoc-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-javadoc-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-src-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-src-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-debuginfo-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-debuginfo-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-demo-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-demo-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-devel-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-devel-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-javadoc-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-javadoc-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-src-1.6.0.0-1.40.1.9.10.el6_1
1.6.0-openjdk-src-1.6.0.0-1.40.1.9.10.el6_1
redhat/java<1.6.0-openjdk-1.6.0.0-1.23.1.9.10.el5_7
1.6.0-openjdk-1.6.0.0-1.23.1.9.10.el5_7
redhat/java<1.6.0-openjdk-1.6.0.0-1.23.1.9.10.el5_7
1.6.0-openjdk-1.6.0.0-1.23.1.9.10.el5_7
redhat/java<1.6.0-openjdk-demo-1.6.0.0-1.23.1.9.10.el5_7
1.6.0-openjdk-demo-1.6.0.0-1.23.1.9.10.el5_7
redhat/java<1.6.0-openjdk-devel-1.6.0.0-1.23.1.9.10.el5_7
1.6.0-openjdk-devel-1.6.0.0-1.23.1.9.10.el5_7
redhat/java<1.6.0-openjdk-javadoc-1.6.0.0-1.23.1.9.10.el5_7
1.6.0-openjdk-javadoc-1.6.0.0-1.23.1.9.10.el5_7
redhat/java<1.6.0-openjdk-src-1.6.0.0-1.23.1.9.10.el5_7
1.6.0-openjdk-src-1.6.0.0-1.23.1.9.10.el5_7
redhat/java<1.6.0-openjdk-demo-1.6.0.0-1.23.1.9.10.el5_7
1.6.0-openjdk-demo-1.6.0.0-1.23.1.9.10.el5_7
redhat/java<1.6.0-openjdk-devel-1.6.0.0-1.23.1.9.10.el5_7
1.6.0-openjdk-devel-1.6.0.0-1.23.1.9.10.el5_7
redhat/java<1.6.0-openjdk-javadoc-1.6.0.0-1.23.1.9.10.el5_7
1.6.0-openjdk-javadoc-1.6.0.0-1.23.1.9.10.el5_7
redhat/java<1.6.0-openjdk-src-1.6.0.0-1.23.1.9.10.el5_7
1.6.0-openjdk-src-1.6.0.0-1.23.1.9.10.el5_7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/java-1.6.0-openjdk to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.23.1.9.10.el5_7
  2. Upgrade

    Upgrade redhat/java-1.6.0-openjdk-debuginfo to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.23.1.9.10.el5_7
  3. Upgrade

    Upgrade redhat/java-1.6.0-openjdk-demo to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.23.1.9.10.el5_7
  4. Upgrade

    Upgrade redhat/java-1.6.0-openjdk-devel to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.23.1.9.10.el5_7
  5. Upgrade

    Upgrade redhat/java-1.6.0-openjdk-javadoc to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.23.1.9.10.el5_7
  6. Upgrade

    Upgrade redhat/java-1.6.0-openjdk-src to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.23.1.9.10.el5_7
  7. Upgrade

    Upgrade redhat/java-1.6.0-openjdk to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.40.1.9.10.el6_1
  8. Upgrade

    Upgrade redhat/java-1.6.0-openjdk-debuginfo to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.40.1.9.10.el6_1
  9. Upgrade

    Upgrade redhat/java-1.6.0-openjdk-devel to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.40.1.9.10.el6_1
  10. Upgrade

    Upgrade redhat/java-1.6.0-openjdk-javadoc to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.40.1.9.10.el6_1
  11. Upgrade

    Upgrade redhat/java-1.6.0-openjdk-demo to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.40.1.9.10.el6_1
  12. Upgrade

    Upgrade redhat/java-1.6.0-openjdk-src to a version that resolves this vulnerability.

    Fixed in 1:1.6.0.0-1.40.1.9.10.el6_1
  13. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-1.6.0.0-1.40.1.9.10.el6_1
  14. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-debuginfo-1.6.0.0-1.40.1.9.10.el6_1
  15. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-demo-1.6.0.0-1.40.1.9.10.el6_1
  16. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-devel-1.6.0.0-1.40.1.9.10.el6_1
  17. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-javadoc-1.6.0.0-1.40.1.9.10.el6_1
  18. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-src-1.6.0.0-1.40.1.9.10.el6_1
  19. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-1.6.0.0-1.23.1.9.10.el5_7
  20. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-demo-1.6.0.0-1.23.1.9.10.el5_7
  21. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-devel-1.6.0.0-1.23.1.9.10.el5_7
  22. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-javadoc-1.6.0.0-1.23.1.9.10.el5_7
  23. Upgrade

    Upgrade redhat/java to a version that resolves this vulnerability.

    Fixed in 1.6.0-openjdk-src-1.6.0.0-1.23.1.9.10.el5_7
  24. Upgrade

    Upgrade java-1.6.0-openjdk to a version that resolves this vulnerability.

    Fixed in 1.9.10
  25. Configuration

    To disable the CBC protection mitigation if it causes compatibility issues, append -Djsse.enableCBCProtection=false to the java command.

    OpenJDK JSSE jsse.enableCBCProtection = false
  26. Operational

    Restart all running instances of OpenJDK Java for the update to take effect.

Event History

Oct 18, 2011
Advisory Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionAffected Software
Sep 13, 2024
Advisory Published
via OSV·07:08 AM
Data Sourced
via OSV·07:08 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of RHSA-2011:1380?

The severity of RHSA-2011:1380 is classified as critical due to the potential for arbitrary code execution via a flaw in the Java RMI registry implementation.

2

How do I fix RHSA-2011:1380?

To fix RHSA-2011:1380, update to the fixed packages of OpenJDK 6 as detailed in the advisory.

3

Which versions of Java are affected by RHSA-2011:1380?

RHSA-2011:1380 affects specific versions of OpenJDK 6 prior to 1.6.0-openjdk-1.6.0.0-1.40.1.9.10.el6_1.

4

What impact does RHSA-2011:1380 have on my system?

The impact of RHSA-2011:1380 could allow an attacker to execute arbitrary code, leading to potential system compromise.

5

Is RHSA-2011:1380 related to remote access vulnerabilities?

Yes, RHSA-2011:1380 is related to remote access vulnerabilities through the exploitation of the RMI registry.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203