CVE-2010-3541: Medium severity Sun JRE vulnerability

Published Oct 12, 2010
·
Updated

Unspecified vulnerability in the Networking component in Oracle Java SE and Java for Business 6 Update 21, 5.0 Update 25, 1.4.227, and 1.3.128 allows remote attackers to affect confidentiality, integrity, and availability 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 is related to missing validation of request headers in the HttpURLConnection class when they are set by applets, which allows remote attackers to bypass the intended security policy.

Affected Software

273 affected componentsFixes available
redhat/java<1.4.2-ibm-0:1.4.2.13.6-1jpp.3.el3
1.4.2-ibm-0:1.4.2.13.6-1jpp.3.el3
redhat/java<1.6.0-sun-1:1.6.0.22-1jpp.1.el4
1.6.0-sun-1:1.6.0.22-1jpp.1.el4
redhat/java<1.4.2-ibm-0:1.4.2.13.6-1jpp.2.el4
1.4.2-ibm-0:1.4.2.13.6-1jpp.2.el4
redhat/java<1.5.0-ibm-1:1.5.0.12.2-1jpp.1.el4
1.5.0-ibm-1:1.5.0.12.2-1jpp.1.el4
redhat/java<1.6.0-ibm-1:1.6.0.9.0-1jpp.3.el4
1.6.0-ibm-1:1.6.0.9.0-1jpp.3.el4
redhat/java<1.6.0-openjdk-1:1.6.0.0-1.16.b17.el5
1.6.0-openjdk-1:1.6.0.0-1.16.b17.el5
redhat/java<1.6.0-openjdk-1:1.6.0.0-1.31.b17.el6_0
1.6.0-openjdk-1:1.6.0.0-1.31.b17.el6_0
redhat/java<1.5.0-ibm-1:1.5.0.12.2-1jpp.1.el6
1.5.0-ibm-1:1.5.0.12.2-1jpp.1.el6
redhat/java<1.6.0-ibm-1:1.6.0.9.0-1jpp.4.el6
1.6.0-ibm-1:1.6.0.9.0-1jpp.4.el6
redhat/java<1.6.0-ibm-1:1.6.0.9.1-1jpp.1.el5
1.6.0-ibm-1:1.6.0.9.1-1jpp.1.el5
redhat/java<1.4.2-ibm-sap-0:1.4.2.13.6.sap-1jpp.1.el4_8
1.4.2-ibm-sap-0:1.4.2.13.6.sap-1jpp.1.el4_8
redhat/java<1.4.2-ibm-sap-0:1.4.2.13.6.sap-1jpp.1.el5
1.4.2-ibm-sap-0:1.4.2.13.6.sap-1jpp.1.el5
redhat/java<1.6.0-sun-1:1.6.0.22-1jpp.1.el5
1.6.0-sun-1:1.6.0.22-1jpp.1.el5
redhat/java<1.4.2-ibm-0:1.4.2.13.6-1jpp.2.el5
1.4.2-ibm-0:1.4.2.13.6-1jpp.2.el5
redhat/java<1.5.0-ibm-1:1.5.0.12.2-1jpp.1.el5
1.5.0-ibm-1:1.5.0.12.2-1jpp.1.el5
redhat/java<1.6.0-ibm-1:1.6.0.9.0-1jpp.3.el5
1.6.0-ibm-1:1.6.0.9.0-1jpp.3.el5
Sun JRE<=1.6.0
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_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 JDK<=1.6.0
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_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
Sun JDK<=1.5.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-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-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-update8
Sun JDK=1.5.0-update9
Sun SDK<=1.4.2_27
Sun SDK=1.4.2
Sun SDK=1.4.2_1
Sun SDK=1.4.2_02
Sun SDK=1.4.2_3
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_8
Sun SDK=1.4.2_9
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
Sun SDK=1.4.2_19
Sun SDK=1.4.2_20
Sun SDK=1.4.2_21
Sun SDK=1.4.2_22
Sun SDK=1.4.2_23
Sun SDK=1.4.2_24
Sun SDK=1.4.2_25
Sun SDK=1.4.2_26
Sun JRE<=1.5.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-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-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.4.2_27
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 JDK<=1.3.1_28
Sun JDK=1.3.0
Sun JDK=1.3.0_01
Sun JDK=1.3.0_02
Sun JDK=1.3.0_03
Sun JDK=1.3.0_04
Sun JDK=1.3.0_05
Sun JDK=1.3.1
Sun JDK=1.3.1_01
Sun JDK=1.3.1_01a
Sun JDK=1.3.1_02
Sun JDK=1.3.1_03
Sun JDK=1.3.1_04
Sun JDK=1.3.1_05
Sun JDK=1.3.1_06
Sun JDK=1.3.1_07
Sun JDK=1.3.1_08
Sun JDK=1.3.1_09
Sun JDK=1.3.1_10
Sun JDK=1.3.1_11
Sun JDK=1.3.1_12
Sun JDK=1.3.1_13
Sun JDK=1.3.1_14
Sun JDK=1.3.1_15
Sun JDK=1.3.1_16
Sun JDK=1.3.1_17
Sun JDK=1.3.1_18
Sun JDK=1.3.1_19
Sun JDK=1.3.1_20
Sun JDK=1.3.1_21
Sun JDK=1.3.1_22
Sun JDK=1.3.1_23
Sun JDK=1.3.1_24
Sun JDK=1.3.1_25
Sun JDK=1.3.1_26
Sun JDK=1.3.1_27
Sun JRE<=1.3.1_28
Sun JRE=1.3.0
Sun JRE=1.3.0-update1
Sun JRE=1.3.0-update2
Sun JRE=1.3.0-update3
Sun JRE=1.3.0-update4
Sun JRE=1.3.0-update5
Sun JRE=1.3.1
Sun JRE=1.3.1-update1
Sun JRE=1.3.1-update2
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 JRE=1.3.1_24
Sun JRE=1.3.1_25
Sun JRE=1.3.1_26
Sun JRE=1.3.1_27
Sun SDK<=1.3.1_28
Sun SDK=1.3.0
Sun SDK=1.3.0_01
Sun SDK=1.3.0_02
Sun SDK=1.3.0_03
Sun SDK=1.3.0_04
Sun SDK=1.3.0_05
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 SDK=1.3.1_24
Sun SDK=1.3.1_25
Sun SDK=1.3.1_26
Sun SDK=1.3.1_27

Remediation

Patch Available

http://www.oracle.com/technetwork/topics/security/javacpuoct2010-176258.html

Event History

Oct 12, 2010
CVE Published
12:00 AM
Data Sourced
10:27 AM
DescriptionSeverityAffected Software
Oct 19, 2010
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description

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-2010-3541?

CVE-2010-3541 is classified as a critical vulnerability due to its potential impact on confidentiality, integrity, and availability.

2

How do I fix CVE-2010-3541?

To remediate CVE-2010-3541, you should upgrade to the latest version of Oracle Java SE or apply the relevant patches provided by Oracle.

3

What versions of Java are affected by CVE-2010-3541?

CVE-2010-3541 affects Oracle Java SE and Java for Business versions 6 Update 21, 5.0 Update 25, 1.4.2_27, and 1.3.1_28.

4

Can CVE-2010-3541 be exploited remotely?

Yes, CVE-2010-3541 can be exploited remotely by attackers to compromise affected systems.

5

What is the potential impact of exploiting CVE-2010-3541?

Exploiting CVE-2010-3541 could lead to unauthorized access, data breaches, and system instability.

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