RMI implementation in OpenJDK uses property java.rmi.server.useCodebaseOnly, which controls whether automatic loading of classes from other sources than local CLASSPATH and location specified in the java.rmi.server.codebase property is permitted. This property previously defaulted to false, allowing dynamic class downloading. This could allow an attacker to make RMI server or registry to execute arbitrary untrusted code. It was demonstrated that this can be used in combination with another Java sandbox bypass flaw to execute code in the remote rmiregistry or GlassFish Server: http://seclists.org/fulldisclosure/2013/Feb/18 http://www.security-explorations.com/en/SE-2012-01-details.html http://www.security-explorations.com/materials/se-2012-01-rmi.zip This update changes the default value of the java.rmi.server.useCodebaseOnly property to true. More details on various RMI properties can be found in: http://docs.oracle.com/javase/7/docs/technotes/guides/rmi/javarmiproperties.html
Public now via Oracle Java SE CPU April 2014: http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html Fixed in Oracle Java SE 7u21 and 6u45.
This change is explicitly noted in the release notes: http://www.oracle.com/technetwork/java/javase/7u21-relnotes-1932873.html#rmichanges From this release, the RMI property java.rmi.server.useCodebaseOnly is set to true by default. In previous releases the default value was false. This change of default value may cause RMI-based applications to break unexpectedly. The typical symptom is a stack trace that contains a java.rmi.UnmarshalException containing a nested java.lang.ClassNotFoundException. For more information, see RMI Enhancements. Additional details are covered by the following "RMI Enhancements" document: http://docs.oracle.com/javase/7/docs/technotes/guides/rmi/enhancements-7.html
Upstream commit, as included in IcedTea7 repositories: http://icedtea.classpath.org/hg/release/icedtea7-forest-2.3/jdk/rev/096ed306159f
OpenJDK7 upstream repositories commit: http://hg.openjdk.java.net/jdk7u/jdk7u-dev/jdk/rev/f098e2297ff1
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Via RHSA-2013:0752 https://rhn.redhat.com/errata/RHSA-2013-0752.html
This issue has been addressed in following products: Red Hat Enterprise Linux 6 Via RHSA-2013:0751 https://rhn.redhat.com/errata/RHSA-2013-0751.html
This issue has been addressed in following products: Supplementary for Red Hat Enterprise Linux 6 Supplementary for Red Hat Enterprise Linux 5 Via RHSA-2013:0758 https://rhn.redhat.com/errata/RHSA-2013-0758.html
This issue has been addressed in following products: Supplementary for Red Hat Enterprise Linux 5 Supplementary for Red Hat Enterprise Linux 6 Via RHSA-2013:0757 https://rhn.redhat.com/errata/RHSA-2013-0757.html
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Via RHSA-2013:0770 https://rhn.redhat.com/errata/RHSA-2013-0770.html
Fixed in IcedTea6 versions 1.11.10 and 1.12.5, and IcedTea7 version 2.3.9: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2013-April/022796.html http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2013-April/022890.html http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2013-April/022985.html
This issue has been addressed in following products: Supplementary for Red Hat Enterprise Linux 5 Supplementary for Red Hat Enterprise Linux 6 Via RHSA-2013:0823 https://rhn.redhat.com/errata/RHSA-2013-0823.html
This issue has been addressed in following products: Supplementary for Red Hat Enterprise Linux 5 Supplementary for Red Hat Enterprise Linux 6 Via RHSA-2013:0822 https://rhn.redhat.com/errata/RHSA-2013-0822.html
This issue has been addressed in following products: Supplementary for Red Hat Enterprise Linux 5 Supplementary for Red Hat Enterprise Linux 6 Via RHSA-2013:0855 https://rhn.redhat.com/errata/RHSA-2013-0855.html
This issue has been addressed in following products: Red Hat Network Satellite Server v 5.5 Via RHSA-2013:1456 https://rhn.redhat.com/errata/RHSA-2013-1456.html
This issue has been addressed in following products: Red Hat Network Satellite Server v 5.4 Via RHSA-2013:1455 https://rhn.redhat.com/errata/RHSA-2013-1455.html