CVE-2013-0425: Critical severity oracle jre vulnerability

Published Feb 2, 2013
·
Updated

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11, 6 through Update 38, 5.0 through Update 38, and 1.4.240 and earlier, and OpenJDK 6 and 7, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Libraries, a different vulnerability than CVE-2013-0428 and CVE-2013-0426. NOTE: the previous information is from the February 2013 CPU. Oracle has not commented on claims from another vendor that this issue is related to incorrect "access control checks" in the logging API that allow remote attackers to bypass Java sandbox restrictions.

Affected Software

241 affected components
ORACLE JRE=1.7.0
ORACLE JRE=1.7.0-update1
ORACLE JRE=1.7.0-update10
ORACLE JRE=1.7.0-update11
ORACLE JRE=1.7.0-update2
ORACLE JRE=1.7.0-update3
ORACLE JRE=1.7.0-update4
ORACLE JRE=1.7.0-update5
ORACLE JRE=1.7.0-update6
ORACLE JRE=1.7.0-update7
ORACLE JRE=1.7.0-update9
Oracle JDK=1.7.0
Oracle JDK=1.7.0-update1
Oracle JDK=1.7.0-update10
Oracle JDK=1.7.0-update11
Oracle JDK=1.7.0-update2
Oracle JDK=1.7.0-update3
Oracle JDK=1.7.0-update4
Oracle JDK=1.7.0-update5
Oracle JDK=1.7.0-update6
Oracle JDK=1.7.0-update7
Oracle JDK=1.7.0-update9
ORACLE JRE=1.6.0-update22
ORACLE JRE=1.6.0-update23
ORACLE JRE=1.6.0-update24
ORACLE JRE=1.6.0-update25
ORACLE JRE=1.6.0-update26
ORACLE JRE=1.6.0-update27
ORACLE JRE=1.6.0-update29
ORACLE JRE=1.6.0-update30
ORACLE JRE=1.6.0-update31
ORACLE JRE=1.6.0-update32
ORACLE JRE=1.6.0-update33
ORACLE JRE=1.6.0-update34
ORACLE JRE=1.6.0-update35
ORACLE JRE=1.6.0-update37
ORACLE JRE=1.6.0-update38
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=1.6.0-update22
Oracle JDK=1.6.0-update23
Oracle JDK=1.6.0-update24
Oracle JDK=1.6.0-update25
Oracle JDK=1.6.0-update26
Oracle JDK=1.6.0-update27
Oracle JDK=1.6.0-update29
Oracle JDK=1.6.0-update30
Oracle JDK=1.6.0-update31
Oracle JDK=1.6.0-update32
Oracle JDK=1.6.0-update33
Oracle JDK=1.6.0-update34
Oracle JDK=1.6.0-update35
Oracle JDK=1.6.0-update37
Oracle JDK=1.6.0-update38
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
ORACLE JRE=1.5.0-update36
ORACLE JRE=1.5.0-update38
Sun JRE=1.5.0
Sun JRE=1.5.0-update1
Sun JRE=1.5.0-update10
Sun JRE=1.5.0-update11
Sun JRE=1.5.0-update12
Sun JRE=1.5.0-update13
Sun JRE=1.5.0-update14
Sun JRE=1.5.0-update15
Sun JRE=1.5.0-update16
Sun JRE=1.5.0-update17
Sun JRE=1.5.0-update18
Sun JRE=1.5.0-update19
Sun JRE=1.5.0-update2
Sun JRE=1.5.0-update20
Sun JRE=1.5.0-update21
Sun JRE=1.5.0-update22
Sun JRE=1.5.0-update23
Sun JRE=1.5.0-update24
Sun JRE=1.5.0-update25
Sun JRE=1.5.0-update26
Sun JRE=1.5.0-update27
Sun JRE=1.5.0-update28
Sun JRE=1.5.0-update29
Sun JRE=1.5.0-update3
Sun JRE=1.5.0-update31
Sun JRE=1.5.0-update33
Sun JRE=1.5.0-update4
Sun JRE=1.5.0-update5
Sun JRE=1.5.0-update6
Sun JRE=1.5.0-update7
Sun JRE=1.5.0-update8
Sun JRE=1.5.0-update9
Oracle JDK=1.5.0-update36
Oracle JDK=1.5.0-update38
Sun JDK=1.5.0
Sun JDK=1.5.0-update1
Sun JDK=1.5.0-update10
Sun JDK=1.5.0-update11
Sun JDK=1.5.0-update11_b03
Sun JDK=1.5.0-update12
Sun JDK=1.5.0-update13
Sun JDK=1.5.0-update14
Sun JDK=1.5.0-update15
Sun JDK=1.5.0-update16
Sun JDK=1.5.0-update17
Sun JDK=1.5.0-update18
Sun JDK=1.5.0-update19
Sun JDK=1.5.0-update2
Sun JDK=1.5.0-update20
Sun JDK=1.5.0-update21
Sun JDK=1.5.0-update22
Sun JDK=1.5.0-update23
Sun JDK=1.5.0-update24
Sun JDK=1.5.0-update25
Sun JDK=1.5.0-update26
Sun JDK=1.5.0-update27
Sun JDK=1.5.0-update28
Sun JDK=1.5.0-update29
Sun JDK=1.5.0-update3
Sun JDK=1.5.0-update31
Sun JDK=1.5.0-update33
Sun JDK=1.5.0-update4
Sun JDK=1.5.0-update5
Sun JDK=1.5.0-update6
Sun JDK=1.5.0-update7
Sun JDK=1.5.0-update7_b03
Sun JDK=1.5.0-update8
Sun JDK=1.5.0-update9
ORACLE JRE<=1.4.2_40
ORACLE JRE=1.4.2_38
Sun JRE=1.4.2
Sun JRE=1.4.2_1
Sun JRE=1.4.2_2
Sun JRE=1.4.2_3
Sun JRE=1.4.2_4
Sun JRE=1.4.2_5
Sun JRE=1.4.2_6
Sun JRE=1.4.2_7
Sun JRE=1.4.2_8
Sun JRE=1.4.2_9
Sun JRE=1.4.2_10
Sun JRE=1.4.2_11
Sun JRE=1.4.2_12
Sun JRE=1.4.2_13
Sun JRE=1.4.2_14
Sun JRE=1.4.2_15
Sun JRE=1.4.2_16
Sun JRE=1.4.2_17
Sun JRE=1.4.2_18
Sun JRE=1.4.2_19
Sun JRE=1.4.2_20
Sun JRE=1.4.2_21
Sun JRE=1.4.2_22
Sun JRE=1.4.2_23
Sun JRE=1.4.2_24
Sun JRE=1.4.2_25
Sun JRE=1.4.2_26
Sun JRE=1.4.2_27
Sun JRE=1.4.2_28
Sun JRE=1.4.2_29
Sun JRE=1.4.2_30
Sun JRE=1.4.2_31
Sun JRE=1.4.2_32
Sun JRE=1.4.2_33
Sun JRE=1.4.2_34
Sun JRE=1.4.2_35
Sun JRE=1.4.2_36
Sun JRE=1.4.2_37
Oracle JDK<=1.4.2_40
Oracle JDK=1.4.2_38
Sun JDK=1.4.2
Sun JDK=1.4.2_1
Sun JDK=1.4.2_2
Sun JDK=1.4.2_3
Sun JDK=1.4.2_4
Sun JDK=1.4.2_5
Sun JDK=1.4.2_6
Sun JDK=1.4.2_7
Sun JDK=1.4.2_8
Sun JDK=1.4.2_9
Sun JDK=1.4.2_10
Sun JDK=1.4.2_11
Sun JDK=1.4.2_12
Sun JDK=1.4.2_13
Sun JDK=1.4.2_14
Sun JDK=1.4.2_15
Sun JDK=1.4.2_16
Sun JDK=1.4.2_17
Sun JDK=1.4.2_18
Sun JDK=1.4.2_19
Sun JDK=1.4.2_22
Sun JDK=1.4.2_23
Sun JDK=1.4.2_25
Sun JDK=1.4.2_26
Sun JDK=1.4.2_27
Sun JDK=1.4.2_28
Sun JDK=1.4.2_29
Sun JDK=1.4.2_30
Sun JDK=1.4.2_31
Sun JDK=1.4.2_32
Sun JDK=1.4.2_33
Sun JDK=1.4.2_34
Sun JDK=1.4.2_35
Sun JDK=1.4.2_36
Sun JDK=1.4.2_37

Event History

Feb 2, 2013
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2013-0425?

CVE-2013-0425 is considered critical as it may allow remote attackers to affect confidentiality, integrity, and availability of affected systems.

2

How do I fix CVE-2013-0425?

To address CVE-2013-0425, users should upgrade to the latest version of Oracle Java SE or apply the patches provided by Oracle.

3

Which software versions are affected by CVE-2013-0425?

CVE-2013-0425 affects Oracle Java SE 7 through Update 11, Java SE 6 through Update 38, and OpenJDK versions 6 and 7.

4

What are the potential risks associated with CVE-2013-0425?

The risks include unauthorized access to sensitive data, manipulation of data, and denial of service attacks affecting system availability.

5

Has CVE-2013-0425 been publicly disclosed?

Yes, CVE-2013-0425 has been publicly disclosed, allowing both security teams and malicious actors to be aware of the vulnerability.

Company

Resources

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