CVE-2009-1094: Critical severity Sun JDK vulnerability

Published Mar 13, 2009
·
Updated

Unspecified vulnerability in the LDAP implementation in Java SE Development Kit (JDK) and Java Runtime Environment (JRE) 5.0 Update 17 and earlier; 6 Update 12 and earlier; SDK and JRE 1.3.124 and earlier; and 1.4.219 and earlier allows remote LDAP servers to execute arbitrary code via unknown vectors related to serialized data.

Affected Software

164 affected componentsFixes available
redhat/java<1.6.0-sun-1:1.6.0.13-1jpp.1.el4
1.6.0-sun-1:1.6.0.13-1jpp.1.el4
redhat/java<1.5.0-sun-0:1.5.0.18-1jpp.1.el4
1.5.0-sun-0:1.5.0.18-1jpp.1.el4
redhat/java<1.5.0-ibm-1:1.5.0.9-1jpp.5.el4
1.5.0-ibm-1:1.5.0.9-1jpp.5.el4
redhat/java<1.6.0-ibm-1:1.6.0.5-1jpp.1.el4
1.6.0-ibm-1:1.6.0.5-1jpp.1.el4
redhat/java<1.6.0-openjdk-1:1.6.0.0-0.30.b09.el5
1.6.0-openjdk-1:1.6.0.0-0.30.b09.el5
redhat/java<1.5.0-sun-0:1.5.0.22-1jpp.1.el4
1.5.0-sun-0:1.5.0.22-1jpp.1.el4
redhat/java<1.6.0-ibm-1:1.6.0.7-1jpp.3.el4
1.6.0-ibm-1:1.6.0.7-1jpp.3.el4
redhat/java<1.6.0-sun-1:1.6.0.13-1jpp.1.el5
1.6.0-sun-1:1.6.0.13-1jpp.1.el5
redhat/java<1.5.0-sun-0:1.5.0.18-1jpp.1.el5
1.5.0-sun-0:1.5.0.18-1jpp.1.el5
redhat/java<1.5.0-ibm-1:1.5.0.9-1jpp.3.el5
1.5.0-ibm-1:1.5.0.9-1jpp.3.el5
redhat/java<1.6.0-ibm-1:1.6.0.5-1jpp.1.el5
1.6.0-ibm-1:1.6.0.5-1jpp.1.el5
Sun JDK<=1.5.0
Sun JDK<=1.6.0
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-update2
Sun JDK=1.5.0-update3
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
Sun JDK=1.6.0-update_10
Sun JDK=1.6.0-update_11
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-update2
Sun JRE<=1.5.0
Sun JRE<=1.6.0
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-update2
Sun JRE=1.5.0-update3
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
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_2
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.3.1_24
Sun JRE=1.3.1
Sun JRE=1.3.1_01
Sun JRE=1.3.1_2
Sun JRE=1.3.1_03
Sun JRE=1.3.1_04
Sun JRE=1.3.1_05
Sun JRE=1.3.1_06
Sun JRE=1.3.1_07
Sun JRE=1.3.1_08
Sun JRE=1.3.1_09
Sun JRE=1.3.1_10
Sun JRE=1.3.1_11
Sun JRE=1.3.1_12
Sun JRE=1.3.1_13
Sun JRE=1.3.1_14
Sun JRE=1.3.1_15
Sun JRE=1.3.1_16
Sun JRE=1.3.1_17
Sun JRE=1.3.1_18
Sun JRE=1.3.1_19
Sun JRE=1.3.1_20
Sun JRE=1.3.1_21
Sun JRE=1.3.1_22
Sun JRE=1.3.1_23
Sun SDK<=1.3.1_24
Sun SDK=1.3.1
Sun SDK=1.3.1_01
Sun SDK=1.3.1_01a
Sun SDK=1.3.1_02
Sun SDK=1.3.1_03
Sun SDK=1.3.1_04
Sun SDK=1.3.1_05
Sun SDK=1.3.1_06
Sun SDK=1.3.1_07
Sun SDK=1.3.1_08
Sun SDK=1.3.1_09
Sun SDK=1.3.1_10
Sun SDK=1.3.1_11
Sun SDK=1.3.1_12
Sun SDK=1.3.1_13
Sun SDK=1.3.1_14
Sun SDK=1.3.1_15
Sun SDK=1.3.1_16
Sun SDK=1.3.1_17
Sun SDK=1.3.1_18
Sun SDK=1.3.1_19
Sun SDK=1.3.1_20
Sun SDK=1.3.1_21
Sun SDK=1.3.1_22
Sun SDK=1.3.1_23
Sun JRE<=1.4.2_19
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 SDK<=1.4.2_19
Sun SDK=1.4.2
Sun SDK=1.4.2_1
Sun SDK=1.4.2_2
Sun SDK=1.4.2_02
Sun SDK=1.4.2_03
Sun SDK=1.4.2_3
Sun SDK=1.4.2_04
Sun SDK=1.4.2_4
Sun SDK=1.4.2_5
Sun SDK=1.4.2_6
Sun SDK=1.4.2_7
Sun SDK=1.4.2_08
Sun SDK=1.4.2_09
Sun SDK=1.4.2_10
Sun SDK=1.4.2_11
Sun SDK=1.4.2_12
Sun SDK=1.4.2_13
Sun SDK=1.4.2_14
Sun SDK=1.4.2_15
Sun SDK=1.4.2_16
Sun SDK=1.4.2_17
Sun SDK=1.4.2_18

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 1.6.0-sun-1:1.6.0.13-1jpp.1.el4
  2. Upgrade

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

    Fixed in 1.5.0-sun-0:1.5.0.18-1jpp.1.el4
  3. Upgrade

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

    Fixed in 1.5.0-ibm-1:1.5.0.9-1jpp.5.el4
  4. Upgrade

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

    Fixed in 1.6.0-ibm-1:1.6.0.5-1jpp.1.el4
  5. Upgrade

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

    Fixed in 1.6.0-openjdk-1:1.6.0.0-0.30.b09.el5
  6. Upgrade

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

    Fixed in 1.5.0-sun-0:1.5.0.22-1jpp.1.el4
  7. Upgrade

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

    Fixed in 1.6.0-ibm-1:1.6.0.7-1jpp.3.el4
  8. Upgrade

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

    Fixed in 1.6.0-sun-1:1.6.0.13-1jpp.1.el5
  9. Upgrade

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

    Fixed in 1.5.0-sun-0:1.5.0.18-1jpp.1.el5
  10. Upgrade

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

    Fixed in 1.5.0-ibm-1:1.5.0.9-1jpp.3.el5
  11. Upgrade

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

    Fixed in 1.6.0-ibm-1:1.6.0.5-1jpp.1.el5

Event History

Mar 13, 2009
Data Sourced
via Red Hat·04:38 PM
DescriptionSeverityAffected Software
Mar 25, 2009
CVE Published
via Red Hat·12:00 AM
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
Data Sourced
via NVD·11:30 PM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

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-2009-1094?

CVE-2009-1094 is considered to have a high severity due to its potential to allow remote LDAP servers to execute arbitrary code.

2

How do I fix CVE-2009-1094?

To fix CVE-2009-1094, you should update to a patched version of the Java SE Development Kit or Java Runtime Environment provided by your vendor.

3

Which versions are affected by CVE-2009-1094?

CVE-2009-1094 affects Java SE Development Kit (JDK) and Java Runtime Environment (JRE) versions 1.5.0 through 1.6.0 update 12 and earlier.

4

Can CVE-2009-1094 be exploited remotely?

Yes, CVE-2009-1094 can be exploited remotely by an attacker using malicious LDAP inputs to execute arbitrary code on the affected system.

5

What precautions should I take to prevent CVE-2009-1094 exploitation?

To prevent exploitation of CVE-2009-1094, ensure that you apply security updates and patches from your Java vendor promptly.

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