First published: Mon Oct 04 2010(Updated: )
Unspecified vulnerability in the Java Naming and Directory Interface (JNDI) component in Oracle Java SE and Java for Business 6 Update 21, 5.0 Update 25, and 1.4.2_27 allows remote attackers to affect confidentiality via unknown vectors. NOTE: the previous information was obtained from the October 2010 CPU. Oracle has not commented on claims from a reliable downstream vendor that this allows remote attackers to determine internal IP addresses or "otherwise-protected internal network names."
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Sun JRE | =1.6.0-update_3 | |
Sun JRE | =1.6.0-update_5 | |
Sun JRE | =1.6.0-update_13 | |
Sun JRE | =1.6.0-update_1 | |
Sun JRE | =1.6.0-update_2 | |
Sun JRE | =1.6.0-update_16 | |
Sun JRE | =1.6.0-update_20 | |
Sun JRE | =1.6.0-update_15 | |
Sun JRE | =1.6.0-update_6 | |
Sun JRE | <=1.6.0 | |
Sun JRE | =1.6.0-update_19 | |
Sun JRE | =1.6.0 | |
Sun JRE | =1.6.0-update_18 | |
Sun JRE | =1.6.0-update_10 | |
Sun JRE | =1.6.0-update_17 | |
Sun JRE | =1.6.0-update_7 | |
Sun JRE | =1.6.0-update_14 | |
Sun JRE | =1.6.0-update_4 | |
Sun JRE | =1.6.0-update_12 | |
Sun JRE | =1.6.0-update_11 | |
OpenJDK | =1.6.0-update_4 | |
OpenJDK | =1.6.0-update_7 | |
OpenJDK | =1.6.0-update_19 | |
OpenJDK | =1.6.0-update_13 | |
OpenJDK | =1.6.0-update_3 | |
OpenJDK | =1.6.0-update_11 | |
OpenJDK | =1.6.0-update_10 | |
OpenJDK | <=1.6.0 | |
OpenJDK | =1.6.0-update_14 | |
OpenJDK | =1.6.0 | |
OpenJDK | =1.6.0-update_17 | |
OpenJDK | =1.6.0-update_5 | |
OpenJDK | =1.6.0-update2 | |
OpenJDK | =1.6.0-update1_b06 | |
OpenJDK | =1.6.0-update_16 | |
OpenJDK | =1.6.0-update1 | |
OpenJDK | =1.6.0-update_15 | |
OpenJDK | =1.6.0-update_12 | |
OpenJDK | =1.6.0-update_18 | |
OpenJDK | =1.6.0-update_6 | |
OpenJDK | =1.6.0-update_20 | |
OpenJDK | =1.5.0-update20 | |
OpenJDK | =1.5.0-update15 | |
OpenJDK | =1.5.0-update18 | |
OpenJDK | =1.5.0-update3 | |
OpenJDK | =1.5.0-update21 | |
OpenJDK | =1.5.0-update11 | |
OpenJDK | =1.5.0-update16 | |
OpenJDK | =1.5.0-update17 | |
OpenJDK | =1.5.0-update9 | |
OpenJDK | =1.5.0-update22 | |
OpenJDK | <=1.5.0 | |
OpenJDK | =1.5.0-update6 | |
OpenJDK | =1.5.0-update14 | |
OpenJDK | =1.5.0-update23 | |
OpenJDK | =1.5.0-update1 | |
OpenJDK | =1.5.0-update4 | |
OpenJDK | =1.5.0-update7 | |
OpenJDK | =1.5.0 | |
OpenJDK | =1.5.0-update12 | |
OpenJDK | =1.5.0-update5 | |
OpenJDK | =1.5.0-update24 | |
OpenJDK | =1.5.0-update2 | |
OpenJDK | =1.5.0-update19 | |
OpenJDK | =1.5.0-update13 | |
OpenJDK | =1.5.0-update8 | |
OpenJDK | =1.5.0-update10 | |
Sun SDK | <=1.4.2_27 | |
Sun SDK | =1.4.2_19 | |
Sun SDK | =1.4.2 | |
Sun SDK | =1.4.2_26 | |
Sun SDK | =1.4.2_10 | |
Sun SDK | =1.4.2_12 | |
Sun SDK | =1.4.2_17 | |
Sun SDK | =1.4.2_14 | |
Sun SDK | =1.4.2_21 | |
Sun SDK | =1.4.2_13 | |
Sun SDK | =1.4.2_6 | |
Sun SDK | =1.4.2_23 | |
Sun SDK | =1.4.2_5 | |
Sun SDK | =1.4.2_1 | |
Sun SDK | =1.4.2_18 | |
Sun SDK | =1.4.2_4 | |
Sun SDK | =1.4.2_22 | |
Sun SDK | =1.4.2_7 | |
Sun SDK | =1.4.2_8 | |
Sun SDK | =1.4.2_25 | |
Sun SDK | =1.4.2_02 | |
Sun SDK | =1.4.2_16 | |
Sun SDK | =1.4.2_11 | |
Sun SDK | =1.4.2_9 | |
Sun SDK | =1.4.2_20 | |
Sun SDK | =1.4.2_3 | |
Sun SDK | =1.4.2_24 | |
Sun SDK | =1.4.2_15 | |
Sun JRE | =1.5.0-update22 | |
Sun JRE | =1.5.0 | |
Sun JRE | =1.5.0-update18 | |
Sun JRE | =1.5.0-update2 | |
Sun JRE | =1.5.0-update13 | |
Sun JRE | =1.5.0-update24 | |
Sun JRE | =1.5.0-update12 | |
Sun JRE | =1.5.0-update8 | |
Sun JRE | =1.5.0-update16 | |
Sun JRE | =1.5.0-update21 | |
Sun JRE | =1.5.0-update11 | |
Sun JRE | =1.5.0-update15 | |
Sun JRE | =1.5.0-update7 | |
Sun JRE | =1.5.0-update3 | |
Sun JRE | =1.5.0-update20 | |
Sun JRE | =1.5.0-update5 | |
Sun JRE | =1.5.0-update14 | |
Sun JRE | =1.5.0-update6 | |
Sun JRE | =1.5.0-update9 | |
Sun JRE | =1.5.0-update1 | |
Sun JRE | =1.5.0-update19 | |
Sun JRE | =1.5.0-update10 | |
Sun JRE | <=1.5.0 | |
Sun JRE | =1.5.0-update4 | |
Sun JRE | =1.5.0-update23 | |
Sun JRE | =1.5.0-update17 | |
Sun JRE | =1.4.2_26 | |
Sun JRE | =1.4.2_7 | |
Sun JRE | <=1.4.2_27 | |
Sun JRE | =1.4.2_16 | |
Sun JRE | =1.4.2_24 | |
Sun JRE | =1.4.2_4 | |
Sun JRE | =1.4.2_2 | |
Sun JRE | =1.4.2_19 | |
Sun JRE | =1.4.2_25 | |
Sun JRE | =1.4.2_15 | |
Sun JRE | =1.4.2_13 | |
Sun JRE | =1.4.2_1 | |
Sun JRE | =1.4.2_8 | |
Sun JRE | =1.4.2_12 | |
Sun JRE | =1.4.2_18 | |
Sun JRE | =1.4.2_22 | |
Sun JRE | =1.4.2_14 | |
Sun JRE | =1.4.2_10 | |
Sun JRE | =1.4.2_17 | |
Sun JRE | =1.4.2_9 | |
Sun JRE | =1.4.2 | |
Sun JRE | =1.4.2_21 | |
Sun JRE | =1.4.2_11 | |
Sun JRE | =1.4.2_23 | |
Sun JRE | =1.4.2_3 | |
Sun JRE | =1.4.2_20 | |
Sun JRE | =1.4.2_5 | |
Sun JRE | =1.4.2_6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-3548 is considered to have a high severity as it can affect the confidentiality of systems using the vulnerable Java components.
To fix CVE-2010-3548, upgrade your Java SE or Java for Business installation to the latest security patch provided by Oracle.
CVE-2010-3548 affects multiple versions including Java SE and Java for Business versions 6 Update 21 and earlier, as well as JDK 1.4.2, 1.5.0, and various updates.
Yes, CVE-2010-3548 can be exploited remotely by attackers through unspecified vectors.
Currently, the best practice is to apply the latest patches as soon as possible to mitigate the risks associated with CVE-2010-3548.