First published: Mon Jun 17 2013(Updated: )
It was discovered that the MBeanServer Introspector of the JMX component did not properly verify the package access. An untrusted Java application or applet could possibly use this flaw to bypass intended package restrictions.
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle Java Runtime Environment (JRE) | <=1.7.0 | |
Oracle Java Runtime Environment (JRE) | =1.7.0 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update1 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update10 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update11 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update13 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update15 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update17 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update2 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update3 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update4 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update5 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update6 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update7 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update9 | |
Oracle JDK 6 | <=1.7.0 | |
Oracle JDK 6 | =1.7.0 | |
Oracle JDK 6 | =1.7.0-update1 | |
Oracle JDK 6 | =1.7.0-update10 | |
Oracle JDK 6 | =1.7.0-update11 | |
Oracle JDK 6 | =1.7.0-update13 | |
Oracle JDK 6 | =1.7.0-update15 | |
Oracle JDK 6 | =1.7.0-update17 | |
Oracle JDK 6 | =1.7.0-update2 | |
Oracle JDK 6 | =1.7.0-update3 | |
Oracle JDK 6 | =1.7.0-update4 | |
Oracle JDK 6 | =1.7.0-update5 | |
Oracle JDK 6 | =1.7.0-update6 | |
Oracle JDK 6 | =1.7.0-update7 | |
Oracle JDK 6 | =1.7.0-update9 | |
Oracle Java Runtime Environment (JRE) | <=1.6.0 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update22 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update23 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update24 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update25 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update26 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update27 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update29 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update30 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update31 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update32 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update33 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update34 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update35 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update37 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update38 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update39 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update41 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update43 | |
Sun JRE | =1.6.0 | |
Sun JRE | =1.6.0-update_1 | |
Sun JRE | =1.6.0-update_10 | |
Sun JRE | =1.6.0-update_11 | |
Sun JRE | =1.6.0-update_12 | |
Sun JRE | =1.6.0-update_13 | |
Sun JRE | =1.6.0-update_14 | |
Sun JRE | =1.6.0-update_15 | |
Sun JRE | =1.6.0-update_16 | |
Sun JRE | =1.6.0-update_17 | |
Sun JRE | =1.6.0-update_18 | |
Sun JRE | =1.6.0-update_19 | |
Sun JRE | =1.6.0-update_2 | |
Sun JRE | =1.6.0-update_20 | |
Sun JRE | =1.6.0-update_21 | |
Sun JRE | =1.6.0-update_3 | |
Sun JRE | =1.6.0-update_4 | |
Sun JRE | =1.6.0-update_5 | |
Sun JRE | =1.6.0-update_6 | |
Sun JRE | =1.6.0-update_7 | |
Sun JRE | =1.6.0-update_9 | |
Oracle JDK 6 | <=1.6.0 | |
Oracle JDK 6 | =1.6.0-update22 | |
Oracle JDK 6 | =1.6.0-update23 | |
Oracle JDK 6 | =1.6.0-update24 | |
Oracle JDK 6 | =1.6.0-update25 | |
Oracle JDK 6 | =1.6.0-update26 | |
Oracle JDK 6 | =1.6.0-update27 | |
Oracle JDK 6 | =1.6.0-update29 | |
Oracle JDK 6 | =1.6.0-update30 | |
Oracle JDK 6 | =1.6.0-update31 | |
Oracle JDK 6 | =1.6.0-update32 | |
Oracle JDK 6 | =1.6.0-update33 | |
Oracle JDK 6 | =1.6.0-update34 | |
Oracle JDK 6 | =1.6.0-update35 | |
Oracle JDK 6 | =1.6.0-update37 | |
Oracle JDK 6 | =1.6.0-update38 | |
Oracle JDK 6 | =1.6.0-update39 | |
Oracle JDK 6 | =1.6.0-update41 | |
Oracle JDK 6 | =1.6.0-update43 | |
Sun JDK | =1.6.0 | |
Sun JDK | =1.6.0-update_10 | |
Sun JDK | =1.6.0-update_11 | |
Sun JDK | =1.6.0-update_12 | |
Sun JDK | =1.6.0-update_13 | |
Sun JDK | =1.6.0-update_14 | |
Sun JDK | =1.6.0-update_15 | |
Sun JDK | =1.6.0-update_16 | |
Sun JDK | =1.6.0-update_17 | |
Sun JDK | =1.6.0-update_18 | |
Sun JDK | =1.6.0-update_19 | |
Sun JDK | =1.6.0-update_20 | |
Sun JDK | =1.6.0-update_21 | |
Sun JDK | =1.6.0-update_3 | |
Sun JDK | =1.6.0-update_4 | |
Sun JDK | =1.6.0-update_5 | |
Sun JDK | =1.6.0-update_6 | |
Sun JDK | =1.6.0-update_7 | |
Sun JDK | =1.6.0-update1 | |
Sun JDK | =1.6.0-update1_b06 | |
Sun JDK | =1.6.0-update2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-2453 has a CVSS score indicating it is a high-severity vulnerability affecting certain versions of the Oracle JRE and JDK.
To fix CVE-2013-2453, users should upgrade to a patched version of the Oracle JRE or JDK that is not vulnerable.
CVE-2013-2453 affects various versions of Oracle JRE and JDK, specifically up to and including version 1.7.0_update21 and certain 1.6.x versions.
CVE-2013-2453 can potentially impact users of untrusted Java applications or applets that exploit this vulnerability to bypass package restrictions.
There are no effective workarounds for CVE-2013-2453; the best mitigation is to update to a secure version.