It was discovered that the CORBA component incorrectly shared PresentationManagers accross different threaded groups and application contexts. An untrusted Java application or applet could use these flaws to bypass Java sandbox restrictions. External Reference: http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html
Upstream commit, as included in IcedTea7 repositories: http://icedtea.classpath.org/hg/release/icedtea7-forest-2.3/corba/rev/c1ed8145c1b8
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:0237 https://rhn.redhat.com/errata/RHSA-2013-0237.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:0236 https://rhn.redhat.com/errata/RHSA-2013-0236.html
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Via RHSA-2013:0246 https://rhn.redhat.com/errata/RHSA-2013-0246.html
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Via RHSA-2013:0247 https://rhn.redhat.com/errata/RHSA-2013-0247.html
This issue has been addressed in following products: Red Hat Enterprise Linux 6 Via RHSA-2013:0245 https://rhn.redhat.com/errata/RHSA-2013-0245.html
Fixed in upstream IcedTea versions IcedTea6 1.11.6, and 1.12.1, and IcedTea7 2.1.5, 2.2.5, and 2.3.6: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2013-February/021708.html http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2013-February/021728.html http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2013-February/021905.html http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2013-February/021876.html Note that version 2.3.5 was tagged in upstream mercurial including the security fixes, but was not released. Only 2.3.6 was released, correcting problem introduced by security patches as included in 2.3.5.